We are sorry for the inconvenience. But, I’m afraid we are unable to replicate the issue even re-tested the plugin on different machines. We will appreciate it if you enable the debugging in WordPress and give another try to the plugin. It will provide some meaningful error details to handle the issue.
Oh well it happens I guess…. Here is the error message
Fatal error: Uncaught TypeError: Return value of Twig\Loader\FilesystemLoader::addPath() must be an instance of Twig\Loader\void, none returned in /home/manicbot/public_html/manicbotanix.com/wp-content/plugins/aspose-doc-exporter/vendor/twig/twig/src/Loader/FilesystemLoader.php:96 Stack trace: #0 /home/manicbot/public_html/manicbotanix.com/wp-content/plugins/aspose-doc-exporter/vendor/twig/twig/src/Loader/FilesystemLoader.php(78): Twig\Loader\FilesystemLoader->addPath(‘/home/manicbot/…’, ‘__main__’) #1 /home/manicbot/public_html/manicbotanix.com/wp-content/plugins/aspose-doc-exporter/vendor/twig/twig/src/Loader/FilesystemLoader.php(45): Twig\Loader\FilesystemLoader->setPaths(Array) #2 /home/manicbot/public_html/manicbotanix.com/wp-content/plugins/aspose-doc-exporter/src/AsposeWordsExporter/ExportEngine.php(120): Twig\Loader\FilesystemLoader->__construct(‘/home/manicbot/…’) #3 /home/manicbot/public_html/manicbotanix.com/wp-content/plugins/aspose-doc-exporter/src/AsposeWordsExporter/HookRegistrar.php(30): AsposeWordsExp in /home/manicbot/public_html/manicbotanix.com/wp-content/plugins/aspose-doc-exporter/vendor/twig/twig/src/Loader/FilesystemLoader.php on line 96
Oh and luckily that is showing when I login as the admin area is broken so I can’t enable anything in there. I’m about to upload an entire new site on the domain and was able to save the xml files via the wordpress export regardless so all is not lost. I’m actually leaving the site broken because its all being changed with a new site in the next few days. Hope that code helps.
Thanks for the above error log. We are investigating the issue and will share our findings soon.
We tried to replicate your reported issue with different environment settings i.e. PHP versions and WordPress versions. But unable to reproduce it. We will appreciate it if you please share your installed plugin list and environment details(PHP version/WordPress version) with us. We will install these plugins along with Aspose.Words Exporter and will try to replicate the issue.
- This reply was modified 1 year, 6 months ago by tilalahmad.
I actually couldn’t tell you now because as I said I was in the process of loading a new site (which is now up). As the admin was broken I didn’t bother restoring the old site and fortunately had CSV files downloaded of the content. Plugins I can remember that might have caused a conflict — WP Fastest Cache, Conditional Menus ? It’s a Divi theme site so maybe something there inline with a plugin. Who knows.
- This reply was modified 1 year, 6 months ago by grantmahy.
Thanks for your feedback. We will further investigate the Aspose.Words Exporter plugin with mentioned plugins.
Would the fact that I am running PHP 7.0.33 cause the problem. Just discovered this in my Cpanel and trying to upgrade to a later php version has caused dramas re error messages such as Warning: Cannot modify header information – headers already sent by (output started at /home/manicbot/public_html/manicbotanix.com/wp-content/themes/Divi-child/functions.php:13) in /home/manicbot/public_html/manicbotanix.com/wp-includes/functions.php on line 6274
Okay I have hired someone to go through the php code on my child theme and found one problem so far: This line:
// return ‘http://manicbotanix.com/manic-botanix-australia-shop/’;
Should have been like this:
wp_safe_redirect( ‘http://manicbotanix.com/manic-botanix-australia-shop/’ );
Also there was “?>” at the end and that shouldn’t have been there so it might have been some bad php code in the child theme that was causing the issue with your plugin. Who knows!!!?? I’ve had to do a pretty large cleanup of the site with CSS and now looking into the php in the child theme because it’s been hacked away at over the years by me and others.
Okay that was the only php error in the child theme. The php guy said besides that the php was perfect and he also said no it wouldn’t cause a plugin to crash a site. Anyway I’m no programmer but because you are so keen to find the issue and had been responsive to the situation I just wanted to give you as much feedback as I could.
Thanks, this additional information will help us to reproduce the issue at our end.
- The topic ‘Broke My Site – Even Broke Admin’ is closed to new replies.