Hey @korndev,
please give this another try with the (just released) 3.5.1.1 version.
Thanks for the quick reply @patrickposner, but I’m still seeing the same results.
@korndev,
alright, I’ve done some further testing now – it looks like you have a firewall (Cloudflare, maybe?) blocking wp_remote_get (which is used to download the actual HTML from the page).
As soon as I attempt to visit the site (programmatically), I receive a 403 Forbidden error – so it’s probably a rule related to “bots”.
You want to disable that (at least temporarily) to allow Simply Static to access the content and build up the HTML files.
@patrickposner I’ve disabled Cloudflare (turned off the proxy) and still running into the same issue. Wondering if some other security is blocking on the server. We’re using GridPane if you have any familiarity with it. I’ve turned off all security though, including the 7G/ModSec firewall and the other security measures implemented that I have control over.
@patrickposner Any other recommendations? I’m still running into the same issue.
Hey @korndev,
not really sure we can help with that – we usually don’t deal with server-side configuration outside of our own platform (there are just too many options/configurations out there).
I would probably start with GridPane and ask if there is something in place that blocks wp_remote_get from fetching data from your own website.
It’s a great company and a fantastic product; I’m sure they can at least shed some light on the problem.
You can also use a backup of the site and utilize a tool like LocalWP for the conversion (assuming it’s a one-off conversion) – this would eliminate all potential pitfalls related to firewalls and security settings.
@patrickposner I didn’t realize you can run this from Local. I just did and got the same results. Any other thoughts?
Appreciate your help!
Plugin Support
sr293
(@sr293)
Hello Justin. Thanks for the additional information. It may be possible that a compatibility issue exists in the environment. If possible, I would recommend starting by unit testing everything in your environment to help determine what may be causing the issue. To do this, start by disabling all plugins except Simply Static, changing your theme to a default WordPress theme, and then running a new full (or single) export to see if Simply Static is able to generate the site correctly. Then, one by one, activate each needed plugin and/or theme, running a new export (full or single) after each activation. Hope this information helps.
@sr293 Seems like it’s the theme that is the issue. Happy to go pro or something to consult with you to figure out how to get this site to export. Let me know what options there are. Thanks!
Plugin Support
sr293
(@sr293)
Hello Justin. I’m happy to hear you may have been able to determine the source of the issue preventing you from exporting your site. Since this appears to be a conflict with your current theme, I would recommend as a first step contacting the developers of the theme to see if they are able to possibly offer a solution that may help.
@sr293 unfortunately, that’s not an option. It’s a custom theme and the dev is no longer accessible.
Plugin Support
sr293
(@sr293)
That’s a bummer to hear that. Unfortunately, this would be something that falls outside the scope of the support we can offer, as this would be a compatibility issue with a custom theme or custom code. If at all possible, it may be worthwhile looking into moving to another theme. If you’re comfortable with PHP, you could explore the server logs to see if anything is being reported that could help point you to what’s causing the issue. I hope this information helps. Thank you for your understanding regarding the limitations of the support we can offer.
Hey @patrickposner and @sr293
I was helping Justin troubleshoot this and it was the following code in the theme that the plugin was choking on:
<!--[if lt IE 7]><html class="no-js ie6 oldie" lang="en"> <![endif]-->
<!--[if IE 7]><html class="no-js ie7 oldie" lang="en"> <![endif]-->
<!--[if IE 8]><html class="no-js ie8 oldie" lang="en"> <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en"> <!--<![endif]-->
After replacing it with just
<html class="no-js" lang="en">
everything worked fine.
Looks like the extract_and_replace_urls_in_html function was parsing that code incorrectly and interpreted it as four opening html tags, thus couldn’t parse anything else after that part.
