Forum Replies Created
-
AuthorPosts
-
NickParticipant
I recommend checking that:
- The production and staging environments are both running PHP 7.1 or higher.
- All plugin files were successfully copied during the migration. (Try deleting Genesis Blocks and reinstalling it.)NickParticipantThank you for the extra information about not running WooCommerce.
Other plugins sometimes use the same “Action Scheduler” (https://actionscheduler.org/ ) feature that WooCommerce uses.
If you installed any plugins since switching to Navigation Pro, those could be triggering the requests and high CPU load.
You could work with your host to disable plugins one at a time to see which one is responsible for the high CPU load.
NickParticipantIf your sites are running WooCommerce, it sounds like the WooCommerce Action Scheduler is running tasks in the background (because of
as_async_request_queue_runner
in the admin-ajax URLs).Navigation Pro and other StudioPress themes do not use the WooCommerce Action Scheduler directly, but actions can be scheduled when you switch to a new theme (which triggers thumbnail regeneration if WooCommerce is active) or update WooCommerce. CPU usage should drop once the actions are complete.
You can try to find out what actions are running or complete by visiting WooCommerce -> Status -> Scheduled Actions.
It would also be worth contacting WooCommerce support for help investigating continued high CPU usage due to WooCommerce actions: https://woocommerce.com/contact-us/
November 8, 2019 at 10:13 am in reply to: What studiopress templates have block home page, wide image, one click set up #494572NickParticipantHi, Kelleen.
These themes currently have Gutenberg and one-click set up support:
- Authority Pro
- Monochrome Pro
- Magazine Pro
- Essence Pro
- Revolution Pro
- Genesis Sample
We plan to update other themes and release new ones too.
NickParticipantHi, Danielle.
It looks like you might be using WPML?
If so, their team has some information here about how to translate archive page intro text in Genesis:
https://wpml.org/forums/topic/genesis-archive-page-text-is-not-appearing-in-string-translation/
If the advice there does not work for you, I recommend following up with the plugin developer for further guidance, but please let us know if you get stuck.
August 22, 2019 at 6:54 am in reply to: New Genesis sidebar in WordPress 5.x editor is not translated #493101NickParticipantHi Eduardo
WordPress suggests generating the extra translation files for JavaScript features such as the new Genesis sidebar using the WP-CLI make-json command. This currently requires using an application on the command line.
If you would prefer not to do this yourself, an upcoming update to the Genesis Translations plugin will bundle the new Spanish translation files for you (using the Spanish translations from the Genesis community translation project). This plugin update should be out in the next week or two.
If you want to generate the files yourself with Genesis 3.1, you can create the extra translation files from your custom Spanish language files like this:
1. Install the WP-CLI application locally or on your web server: https://wp-cli.org/#installing. Installing on a production site requires SSH/command line access to the server. Not all web hosts provide this, so you may have to download Genesis to your own computer and generate the files locally.
2. Put your generated es_ES.mo and es_ES.po files in the genesis/lib/languages directory.
3. On the command line, change directory to the Genesis folder: cd /full/path/to/wordpress/wp-content/themes/genesis
4. On the command line, type wp i18n make-json lib/languages to generate the additional language files.
You will see a lot of new files in the genesis/lib/languages directory that look like this:
es_ES-1b2842785614509f830e0f0248f6ae0e.json
es_ES-33894816a3c53f8f3ea09f189fcf974e.json
es_ES-3efe3061bc0c159ec26a0ce5d7ed3aa7.json
es_ES-5d7d3bcd7be019bded372818f3f3b16e.json
es_ES-64f35610e8ac0134b0c2deb3f02c3140.json
es_ES-79dd439c690538ecd94ef8318a920d4f.json
es_ES-9122b2e85854443a5866323841eaed9e.json
es_ES-9bfe8d27585d1f0d45522660f5c452fe.json
es_ES-9c9d9cf90f1fff6210099a3a9fc68f0c.json
es_ES-a81a835585aa480b4ce1da8327dfa0f1.json
es_ES-b0a5690d606ec01a631f92909923e5dc.json
es_ES-e50cb84d4d0ac72d6d5cf1d2a3efedf5.json
es_ES-e9f83c28e273e4218ee08d9d2e9e252d.json
es_ES-ec05fc9d6aa7f97f415999731a8feaad.jsonYou will need to rename each of those files so they start with genesis- like this instead:
genesis-es_ES-1b2842785614509f830e0f0248f6ae0e.json
genesis-es_ES-33894816a3c53f8f3ea09f189fcf974e.json
genesis-es_ES-3efe3061bc0c159ec26a0ce5d7ed3aa7.json
genesis-es_ES-5d7d3bcd7be019bded372818f3f3b16e.json
genesis-es_ES-64f35610e8ac0134b0c2deb3f02c3140.json
genesis-es_ES-79dd439c690538ecd94ef8318a920d4f.json
genesis-es_ES-9122b2e85854443a5866323841eaed9e.json
genesis-es_ES-9bfe8d27585d1f0d45522660f5c452fe.json
genesis-es_ES-9c9d9cf90f1fff6210099a3a9fc68f0c.json
genesis-es_ES-a81a835585aa480b4ce1da8327dfa0f1.json
genesis-es_ES-b0a5690d606ec01a631f92909923e5dc.json
genesis-es_ES-e50cb84d4d0ac72d6d5cf1d2a3efedf5.json
genesis-es_ES-e9f83c28e273e4218ee08d9d2e9e252d.json
genesis-es_ES-ec05fc9d6aa7f97f415999731a8feaad.jsonYou should then find that Genesis picks up the translations in the sidebar:
The StudioPress team is looking at ways to reduce the amount of work to create and download translations in future versions of Genesis. I hope this information is helpful for now.
NickParticipantGenesis 3.0.1 is out now.
It prevents the need to make changes to the CHILD_THEME_NAME, and solves some issues caused by missing page templates.
NickParticipantGenesis 3.0.1 is out now.
It prevents the need to make changes to the
CHILD_THEME_NAME
, and solves some issues caused by missing page templates.NickParticipantThanks for sharing these reports. We’re looking at a potential fix for background images disappearing that would be part of a 3.0.1 update.
A temporary fix for now is to make sure the
CHILD_THEME_NAME
in functions.php matches your stylesheet Theme Name (in the style.css header info).For example, if you have this in functions.php:
define( 'CHILD_THEME_NAME', 'Altitude Pro Theme' );
But your style.css file header says this:
Theme Name: Altitude Pro
You can fix the issue by updating your functions.php with this:
define( 'CHILD_THEME_NAME', 'Altitude Pro' );
As a matter of fact, it not only removed images but completely bricked some of my clients' sites which are now displaying "The site is experiencing technical difficulties."
This sounds like separate to the background removal issue. If you can gain access to PHP error logs, we'd love to learn more. You can share them here or at https://my.studiopress.com/help/.
NickParticipantThanks for testing Genesis 3.0 during the beta, mmjaeger.
We have a fix for this issue to prevent
wp_kses_post
being used on footer widgets that should be in the next beta, or in the release candidate.August 8, 2018 at 2:11 am in reply to: Essence Pro theme: how to show descriptions at beginning of Category pages? #222315NickParticipantThe category description issue was corrected in Essence 1.0.2. (Your site is running 1.0.1.)
You can download a fresh copy of Essence Pro here: https://my.studiopress.com/downloads/
Upgrade instructions for child themes are available here: https://my.studiopress.com/documentation/frequently-asked-questions/genesis-framework-faqs/do-i-need-to-update-my-child-theme/#what-if-i-want-to-update-my-child-theme
Updating child themes is not usually required unless an update solves an issue you're experiencing, as is the case here.
NickParticipantI replied by email, Alex, but just to follow up here in case it helps anyone else.
You'll need to use
wp_logout_url()
instead of hard coding the logout link.This appends a security nonce to the logout url, which prevents the redirect to the “you are attempting to log out” screen you mentioned.
March 23, 2018 at 9:03 am in reply to: Jump links not working properly on Monochrome pro theme #218280NickParticipantTo prevent the target link appearing under the sticky header, you can try adding this CSS to your theme or to Appearance -> Customize -> Additional CSS:
:target:before { content: ""; display: block; height: 70px; margin: -70px 0 0; }
September 30, 2016 at 3:23 pm in reply to: Need to revert to Genesis prior to 2.4: download? #194055NickParticipantVersion 2.4.1 is now out, which solves the content limit issue with the Featured Post and Page widget.
If you don't see it at Dashboard -> Updates already, check back soon.
If you continue to see issues or need further help, please do open a support ticket: https://my.studiopress.com/help/
NickParticipantYou're welcome, Chris! Glad I could help.
NickParticipantIt looks as if your sites contain a malformed link in the Simple Social Icons widget. The email icon contains a link in this format:
<a href="http://[email protected]"></a>
If you edit your Simple Social Icon widget settings to use this URL format instead for the Email URI, that should solve things:
mailto:[email protected]
instead of this:
http://[email protected]
The reason for this is that Edge currently throws an error when parsing href attributes that contain a username due to this bug: https://connect.microsoft.com/IE/feedback/details/2011466/accessing-properties-of-an-htmlanchorelement-with-an-embedded-username-results-in-a-security-error
This error prevents the theme's backstretch JavaScript from running correctly, which is what displays the homepage header image.
January 16, 2015 at 11:45 am in reply to: Google’s New Structured Data Tool – Errors Galore on StudioPress Demo #137684NickParticipant@Scott I haven't had a reply to my post on Google's Forum about these errors yet, but the “empty node” warnings seem like they could be a bug in Google's shiny new structured data testing tool (because the nodes aren't actually empty).
For now, it may be worth using their old structured data tool at http://www.google.com/webmasters/tools/richsnippets, at least until the new one is ironed out a little.
I'll track the post in Google's forum and feed any important comments back to the Genesis developers, though!
November 24, 2014 at 3:47 am in reply to: A request to increase the three links per post limit #132654NickParticipantHi Emma!
If you log in to your My StudioPress account at http://my.studiopress.com and then visit the Pro Plus page at http://my.studiopress.com/pro-plus/ , you should find that you automatically see the discounted amount there (around $299.96 instead of $399.95). If you were expecting a further discount, then the StudioPress team should be able to help out!
You've posted in the “forum bugs” section, by the way. To create a new post in the future you can visit any subform, then scroll to the bottom and fill out the form to create a new entry. That way you're not adding to someone else's post and it's more likely that your enquiry will be seen. I hope that helps!
NickParticipantYep, it looks like filtering the posts_per_page in pre_get_posts is the way to do it! Well done for your perseverance, thanks for posting your solution, and I'm really happy that you managed to solve it!
NickParticipantDoes it work if you use the pre_get_posts filter in your template? Something like this before your main loop function:
add_filter( 'pre_get_posts', 'my_archive_query' ); function my_archive_query( $query ) { $query->set( 'posts_per_page', 20 ); }
(You could then remove the 'posts_per_page' parameter from the array in your main loop.)
There's an interesting WordPress trac ticket here that you may like to read: https://core.trac.wordpress.org/ticket/16168 It suggests that pagination in archive template loops only works if the query is modified using the pre_get_posts filter.
-
AuthorPosts