Forum Replies Created
October 9, 2021 at 8:17 am in reply to: Updating PHP: does it have anything to do with StudioPress themes? #504526
PHP is the programming language in which WordPress, the Genesis Framework, and child themes are written. The Genesis Framework is designed to run on PHP version 7.1 or higher. I have all of my sites running on 7.4 and I manage a loy of sites. In my development environment, I sometimes use 8. I haven't had any issues with Genesis or its child themes on any of the higher PHP versions.
What you may run into is problems with custom code and 3rd party plugins. Developers generally write code for the current version of PHP. Functions that work in older versions of PHP may be deprecated and later removed in newer versions. This means that if a new version of PHP displays errors originating in custom code, the custom code may have to be rewritten.
The same holds true for plugins. I don't use 8 much in my development environment because quite a few WordPress 3rd-party plugins are not compatible with 8 yet. If you upgrade to 8 and have plugin issues, downgrade to 7.4.
As a rule, we create a separate staging or development environment to test major upgrades such as a new version of PHP. You shouldn't have any problems upgrading to 7.4. If you decide to go to V8, do yourself a favor and clone your production environment and upgrade the cloned environment first so you can test without impacting your production environment.
September 29, 2021 at 12:02 pm in reply to: Theme Error causing code to appear on the site and on the backend. #504497September 29, 2021 at 12:01 pm in reply to: Theme Error causing code to appear on the site and on the backend. #504496
That code doesn't look like anything that would come from Genesis. When I look at the page's source code, the error is happening after the opening body tag. Then after the error are all of the meta tags that belong in the header area appear. The first misplaced code belongs to Yoast. I think you've got a plugin messing up that page's proper order.
I would deactivate Yoast first, then other plugins in order. If the problem is still there after refreshing the screen after each plugin deactivation, then work on the theme. Change to a default WordPress theme and see what happens.
I know it's laborious to test things this way, but there's no alternative of which I'm aware.
September 20, 2021 at 7:22 am in reply to: Can anyone help me with the Team page on Infinity Pro? #504467
Can't access your site:
accessbis.com.au uses an invalid security certificate.
The certificate is not trusted because it is self-signed.
Error code: MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT
You say you have a problem in two sections, but you never state what it is that you perceive as a problem. The website looks great as it is. What are you trying to accomplish?
August 30, 2021 at 6:12 am in reply to: Advanced Columns – How to Equalise Heights of Columns #504426August 28, 2021 at 6:05 am in reply to: WordPress 5.8, Genesis v 3.3.4 and Block-based Widget Editor #504424
You can use your own block based widgets. The new widget editor was disabled because the Genesis widgets don't work with them. If you're not using Genesis widgets, you can unblock the Genesis block.
I recently ran into this same issue on one of the sites I manage. Fontawesome has been going through significant revisions and some of the reference IDs for icons have changed. You have to locate the icon on the Fontawesome website and use the new ID for the icons you want.
Genesis stopped using the blog template quite awhile ago. You have enable the custom fields panel on the editor's preference screen and then use query_args. This is the second method referenced in the document you posted.
If you're using ACF, you won't be able to enable the custom fields panel in the editor.
August 25, 2021 at 5:15 am in reply to: Infinity Pro, WooCommerce; 4 instead of 2 related products columns #504415
Did you contact Studio Press as Woo suggested? This is a community form where questions are answered by volunteers with no affiliation with Studio Press. We're end users just like you.
WordPress doesn't support SVGs natively, but I use SVG images and icons wherever I can in my WordPress sites. I use this plugin to add SVG support: https://wordpress.org/plugins/svg-support/
August 21, 2021 at 3:45 am in reply to: WordPress 5.8, Genesis v 3.3.4 and Block-based Widget Editor #504404
The Genesis developers disabled the widget editor because Genesis widgets are not compatible yet. Try updating to the latest version of Genesis (3.3.5). It might make a difference.
It doesn't look like you can use both at the same time. The error you are getting is because you have 2 plugins calling a function with the same name, genesis_blocks_load(). PHP requires that all functions in a system have unique names unless preceded by a namespace declaration.
August 6, 2021 at 5:36 am in reply to: Moving "read more" link in archives to "genesis_after_entry_content" #504383
There's a difference between actions and filters. Bill's code is manipulating filters, which means the more link is being changed at the place in the Genesis code where the corresponding apply_filters function is installed. Filters always return content.
Actions on the other hand, generally don't return content, but are used for executing one of more add_actions based on their priority in the corresponding do_action queue.
Don't hold me to this, but I don't think the genesis_after_entry_content is going to work for the read more link. All the filters in Bill's code are called within the "loop". The loop is where post content is pulled from the database and prepared for display on the front end. I could be wrong about this, but I believe genesis_after_entry_content executes after the loop has completed. After the loop, the more link won't have access to the appropriate content. If you can get this to work, I'd be interest to know your result. It's not anything I would even try.
The Genesis development team stopped including sitemap templates with their themes quite some time ago. I use the HTML sitemap generated from my SEO plugin. I use SEOPress Pro, but almost all SEO plugins should provide the sitemap capability.
There is no js directory that comes with the Genesis Sample theme. So, a 404 response is correct for this theme. The question is, where is this link coming from? It could be coming from custom programming that someone attempted before you owned the site. I would look at functions.php or files that are loaded in functions.php for custom code. If that doesn't work, are there any custom plugins?
If I were troubleshooting this, I would download the entire theme directory to my local environment and use the search tools on my Mac so I can see if that text string is anywhere in any theme file.
August 4, 2021 at 6:41 am in reply to: Which still actively supported theme most closely resembles Academy Pro? #504370
You should look at the available themes and make a choice that suits your aesthetic. However, I think Navigation Pro or Authority Pro may be a fit for your purpose.
On another note, I use Academy Pro on multiple sites and all are upgraded to the latest versions of WordPress and Genesis. I don't have problems or errors on any of these sites.
If you are experiencing problems, it may not be due to Academy Pro at all, but some other issue with any custom programming or plugin. Even recently deprecated child themes will continue working for a long time because their core functionality derives from the Genesis Framework, not the child theme itself. A child theme just provides the look and feel.
Also, I understand your frustration, but this a community supported site. I don't know for certain that WP Engine or Studio Press resources even review the posts here. We're all community volunteers that answer questions on this site and have no affiliation with Studio Press.
I run Academy Pro on one of my sites without issue. The site is fully updated.
Genesis child themes derive their functionality from the Genesis Framework. A change to WordPress shouldn't impact a child theme unless there is custom coding that bypasses the Genesis Framework and directly uses WordPress functions. Other than that, Genesis is kept up to date to work with the latest versions of WordPress.
The latest version of Genesis disables the new Gutenberg based widget editor because some of its widgets are incompatible with the new editor. You can enable the new editor on if you're not using Genesis widgets on your site.
I think the greatest impact to child themes is yet to come and won't be apparent until WordPress enables the front end editing feature. From my limited understanding, front end editing will require a block based theme to work correctly.