I just updated from Royal version 6.3.3 to 6.3.8 and immediately reveiced an automated notification from WordPress that there is a critical problem on page https://www.companyname.fi/wp-admin/admin-ajax.php?action=heartbeat
File /data/wordpress/htdocs/wp-content/themes/royal/framework/init.php row 46 an error was detected E_COMPILE_ERROR. Error message: require_once(): Failed opening required ‘/data/wordpress/htdocs/wp-content/themes/royal/framework/inc/envato_setup/envato_setup.php’ (include_path=’.:/usr/share/php’)
I rolled back to 6.3.3 for now but 6.3.8 is still installed on the staging site.
I am using an older product code that was bought separately from Envato Market, but since I have later bought the life-long license here, I also have a newer product code. Should I switch to using the newer product code, or is there some other problem and how do we fix it?Site URL: hidden Theme version: 6.3.8 WooCommerce version: 6.3.1
Thank you for getting in touch with us.
Please provide us with temporary wp-admin and FTP access to the staging site with the problem.
To provide wp-admin access, you can create a new user account with administrator role via the Dashboard, and provide us with the username and password via the Private Content area.
To create FTP access, please contact your hosting provider for assistance.
Thank you for your cooperation and we look forward to hearing from you soon.
Thank you for your reply!
To be clear, if you fix the problem on the staging site, how will we implement the fix to the production site?
Should I make credentials to the production site instead, and would you like to update the theme again yourself there? Or do you want to investigate the problem on the staging site first?
I only received the notification from WordPress when I updated the theme in production.
Please let me know, which site’s access (production or staging) you need.
We kindly request access to both sites so that we can investigate the issue and apply the fix to the staging site first, followed by the production site.
Thank you for your cooperation.
Please see the Private content area.
Thank you for your response.
We have successfully resolved the bug on both sites (themes/royal/framework/init.php).
The fix will be included in the next update also.
I am glad to hear it! But I rolled the production site back to theme version 6.3.3 before I contacted you, and the problem occured only when 6.3.8 was used.
So, how can I update production to 6.3.8 and get the bug fix implemented?
The latest version of the theme and Royal Core plugin you can download from this page https://www.8theme.com/downloads and re-upload on your site to fix the problem.
If I delete the old theme folder and re-upload the new theme folder, it will replace the init.php that you have fixed. Please clarify, how can I update production to the new theme version without overwriting the fixed file.
Do I copy the init.php from the staging site and paste it to production after uploading the new theme version?
The latest version on this page https://www.8theme.com/downloads contains the fix in init.php. All should be fixed after the theme update.
I see! The download section had the same 6.3.8 version number and showed that it had been updated in February, so I didn’t know you had updated the theme there.
Now I updated the production site successfully. Thank you for the help!
The topic ‘Critical Problem with New Royal Version’ is closed to new replies.
One standard license is valid only for 1 project. Running multiple projects on a single license is a copyright violation.