- This topic has 4 replies, 3 voices, and was last updated 10 years, 9 months ago by .
Viewing 5 posts - 1 through 5 (of 5 total)
Viewing 5 posts - 1 through 5 (of 5 total)
- You must be logged in to reply to this topic.
Support site for Tips and Tricks HQ premium products
by
Tips and Tricks HQ Support Portal › Forums › WP PDF Stamper › Activating PDF Stamper after site migration results in white screen
Tagged: pdf stamper
I migrated a site from HostGator to Site5 that has eStore and PDF Stamper. When PDF Stamper is activated I cannot load the front end of the site, I get a white screen. Site5 already has Ioncube on their servers and the Minimum Requirement Checker passes. I tried uninstalling and reinstalling the plugin to no avail, no plugins are active except Min. Req. Checker, eStore and PDF Stamper. I tried with only PDF Stamper activated, still got the white screen. I switched theme to Twenty Twelve, same thing. I installed eStore and PDF Stamper on a test WordPress install also on Site5 and the test site loads fine.
I used the Duplicator plugin to clone the site. WordPress 3.8.1, eStore v.6.9.6.8, PDF Stamper version 4.1.9. The original site on HG works fine. I spent hours banging my head and I don’t know what I’m missing.
Hi, can you please connect to your new site via FTP and check if there is any error
log file?
Did you upload the plugin via the WordPress’s plugin uploader?
What is the PHP Memory limit on the new host?
What version of PHP is the new host using?
Also try doing the following:
https://support.tipsandtricks-hq.com/forums/topic/re-install-or-load-a-fresh-build-of-the-plugins
The error log is blank.
Yes, I uploaded the plugin from within WordPress.
The PHP memory limit is 256M.
PHP version 5.3.27
I’ll get a fresh link to the latest version of the plugin and uninstall/reinstall and report back…
I installed the latest version of the plugin and still get the white screen when I go to the home page. The server passes the Minimum Requirement Checker plugin test. Still doesn’t work with all other plugins deactivated and the theme set to Twenty Twelve. I’m thinking it has to do with something on the host (Site5).
Yeah something on the host is conflicting. It would be good if the error reporting was turned on. That way we could have some info on what it is. Can you ask your host to turn on the error reporting temporarily so we can see some output with error/warning details?