-
AuthorPosts
-
July 22, 2024 at 10:01 pm #1462708
I was running the latest version of Enfold 5x series. Upon upgrading I am getting the following errors on some of my archive pages:
July 22, 2024 at 10:16 pm #1462709I’ve reverted back to an older version of the theme for now.
July 23, 2024 at 4:18 am #1462735Hi,
Thank you for the inquiry.
Please clone the site to a staging or dev environment, upgrade to the latest version, and post the login details in the private field so that we can check the issue properly.
Best regards,
IsmaelJuly 28, 2024 at 5:28 am #1463143Thanks, login details below:
July 28, 2024 at 2:43 pm #1463152Hi,
Thank you for the link to your site, I see that switching to the parent theme v6.0.2 solves the error, so this points to an error in one of your child theme files.
Try removing these files via FTP and then add them back in one at a time to find the error, then review your customized file with the current theme version to find the difference.
Our latest updates adds a lot of new features including ACF integration, so your customized theme files will probably need to be updated.Best regards,
MikeJuly 28, 2024 at 7:55 pm #1463173The error appears to be caused by this line in my functions.php:
//Disable Portfolio custom post type add_action( 'after_setup_theme', 'remove_portfolio' ); function remove_portfolio() { remove_action( 'init', 'portfolio_register' ); }
Is there another way to accomplish this in version 6.0.2?
July 28, 2024 at 8:20 pm #1463176Hi,
When I test this on my site the only time I see and error is if I try to use a portfolio element.
So if you want to disable the portfolio CPT you should ensure to not use a portfolio element.Best regards,
MikeOctober 13, 2024 at 3:49 am #1469006I understand. But I want to entirely disable the the portfolio custom post type so I don’t see it at all on the admin side.
Is it possible that the way Enfold manages custom post types, especially the portfolio post type, has changed between versions, and your code for disabling the portfolio is no longer compatible with the latest version?
- This reply was modified 1 month, 1 week ago by cmactv.
October 13, 2024 at 3:59 am #1469009It looks like changing the code in my functions.php to this:
// Disable Portfolio custom post type add_action( 'init', 'remove_portfolio', 20 ); function remove_portfolio() { unregister_post_type( 'portfolio' ); }
Has resolved the error. Do you see any issues with this?
October 13, 2024 at 2:31 pm #1469021Hi,
This looks fine, glade you found a solution, shal1 we close this thread then?Best regards,
MikeOctober 13, 2024 at 10:53 pm #1469043Thank you. I discovered another issue, but it was due to the new taxonomy.php file. Since you introduced this new file, it would be good to have some settings in Theme Options for blog layout. Since it does not respect that setting.
October 14, 2024 at 4:39 am #1469052Hi,
it was due to the new taxonomy.php file. Since you introduced this new file, it would be good to have some settings in Theme Options for blog layout.
The taxonomy.php file has been there for quite a while. What seems to be the issue with it? Please open a new thread if you’re still encountering the problem. We’ll close this thread for now.
Thank you for your patience.
Best regards,
Ismael -
AuthorPosts
- You must be logged in to reply to this topic.