March 29, 2019 at 9:24 pm #1084734
Greetings! Tried posting this already, but did not see on the site, apologies if this is a dual post.
We are getting the error shown in the Private Area when we try to add a new page or post in the Propulsion theme, and cannot seem to find the source of the problem. We tested all plugins and changed themes to troubleshoot. We identified some sort of Propulsion theme issue as being the cause of the problem, because the issue does not occur when we change the theme to one of the WordPress default themes.
We are using the technology shown in the private area.
Any help to further troubleshoot or fix the issue is appreciated, thanks!April 1, 2019 at 9:32 am #1085375
Please send us a temporary admin login and login URL so that we can have a closer look. You can post the details in the Private Content section of your reply. Please note that we are actively phasing out Propulsion, that means it won’t get any updates from now on. If you have bought the theme recently then you might be able to get a refund.
RikardApril 1, 2019 at 5:08 pm #1085581April 3, 2019 at 7:30 am #1086396
Please try using php7.0 and see if the issue persists.
VictoriaApril 3, 2019 at 11:08 pm #1086685April 4, 2019 at 10:00 am #1086921
Alright. We’ll keep the thread open.
You might want to consider Enfold as your next theme of choice.
IsmaelApril 5, 2019 at 4:51 pm #1087510April 8, 2019 at 4:17 am #1088114
Thanks for the update. We would like to login and check the issue further, but the site url is missing from your previous reply. What is the complete error? Does it point to specific line of code in a file?
You have to rebuild the pages from scratch and reconfigure the options if you decide to switch to Enfold because it has a different layout or template builder. You will however save a lot of time in the long run because Enfold is much more advance and easier to use in comparison to a lot of themes.
IsmaelApril 11, 2019 at 4:59 pm #1089623April 12, 2019 at 2:34 am #1089818
Thanks for the update.
Did you set WP to debug mode?
You can just add this code in the wp-config.php file.
// Enable WP_DEBUG mode define( 'WP_DEBUG', true ); // Enable Debug logging to the /wp-content/debug.log file define( 'WP_DEBUG_LOG', true ); // Disable display of errors and warnings define( 'WP_DEBUG_DISPLAY', true); // Use dev versions of core JS and CSS files (only needed if you are modifying these core files) define( 'SCRIPT_DEBUG', true );
After adding the code, refresh the page and you should see the actual error. You can also check the error logs in the root directory. We may need to access the file server in order to help you debug the issue. Please post the FTP details in the private field.
IsmaelApril 12, 2019 at 6:33 pm #1090119April 13, 2019 at 8:51 am #1090311
Please place them along with the other define entries in the file, I don’t think the order of them should matter. Just make sure that there are no duplicates of anything.
RikardApril 22, 2019 at 10:28 pm #1093414April 24, 2019 at 4:35 am #1093821
Thanks for the update.
The error is a bit obscure or it doesn’t specify the where it occurs directly. Would you mind if we access the file server? Please post the FTP details in the private field so that we can check the files and do further debugging.
IsmaelApril 24, 2019 at 6:09 pm #1094094
You must be logged in to reply to this topic.