mmosehauer
Forum Replies Created
-
Forum: Plugins
In reply to: [Apester Interactive Content] TinyMCE errorIn my case, this is the plugin which breaks when Apester v2.1.4 is installed: https://ww.wp.xz.cn/plugins/mce-table-buttons/
Forum: Plugins
In reply to: [WP2Static] Deploying to a subdirectory not working@markwp2static To be clear, I still haven’t been able to deploy to a subdirectory, and I still have not heard back from [email protected]. Here’s more info about my issue (this info was sent to [email protected]):
I have tried testing the plugin locally and on a staging environment— in both cases, the plugin is not exporting the majority of my site’s pages. In both cases I attempt to export to a subdirectory on the current server.
On my staging environment, I get the following in the export log for the majority of pages:
BAD RESPONSE STATUS (401)I tested further locally. Locally, I get a similar response for the majority of pages in the export log. For example, for the homepage I get the following:
Crawling / cURL error:Failed to connect to 127.0.0.1 port 8080: Connection refused NOT SAVING EMTPY FILE / Memory allocated by crawl script: 3328 Exclusion rules wp-jsonHowever, I get a handful of successful pages. The successful pages are all WP category pages, WP tag pages, or .xml pages. For example:
Crawling /category/news/page/1 SAVING /category/news/page/1 to /var/www/html/wp-content/uploads/wp-static-html-output-1568057239/category/news/page/1/index.html Memory allocated by crawl script: 3328 Exclusion rules wp-jsonThe successful pages look great, but again, crawling the majority of my site’s pages result in an error.
Forum: Plugins
In reply to: [WP2Static] Deploying to a subdirectory not workingHi @damhnait — I reached out to [email protected] and was told that my issue will be worked on, but I have not received any help yet. If/when I do receive help and find a solution, I will update this thread.
Forum: Plugins
In reply to: [WP2Static] Deploying to a subdirectory not workingI also attempted to export my site to a ZIP archive, which again took approx 12 minutes, and upon completion the only file which was actually exported was the site’s robots.txt. That leads me to believe the robots.txt file is not allowing the plugin to crawl / export the site, but I’m not sure how to proceed. Any help is appreciated.
Thanks, John.
Here are all the plugins that were active on the site at the time of activation:
- ACF Content Analysis for Yoast SEO
- Advanced Ads
- Advanced Ads Pro
- Advanced Ads – Sticky Ads
- Advanced Custom Fields PRO
- Advanced Custom Fields: Table Field
- Analytics for WordPress — by Segment.io
- Autoptimize
- BJ Lazy Load
- Classic Editor
- Compress JPEG & PNG images
- CookieMonster
- Duplicate Post
- MCE Table Buttons
- Native PHP Sessions for WordPress
- Pantheon Advanced Page Cache
- Redirection
- Related Posts
- Robots.txt rewrite
- Share Buttons by AddThis
- Stop User Enumeration
- WordPress Importer
- WP Media folder
- WP Redis
- Yoast SEO Premium
More details:
Once the plugin files were deleted via Pantheon, the site would load, but the front-end was stuck in a constant re-load state. It would load and immediately re-load indefinitely. At this time, the site was presumably being loaded by Pantheon CDN, so I am assuming that at this time the ‘Autoclear Autoptimize Cache’ plugin was possibly still playing a role. While in the constant re-load state, it also appeared that an old version of the Autoptimize js file was being loaded on the page, because there were console errors relating to js functions not being defined that have in fact been defined for awhile. Once Pantheon cache was flushed (presumably fully removing the ‘Autoclear Autoptimize Cache’ plugin), the constant re-load stopped, and console errors were gone.
Hope that helps. Any insight would be much appreciated!
That explanation helps, thanks! I’ve reached out the companion plugin’s support, and hopefully they can provide further insight.
Here’s the support topic I created on the Autoclear Autoptimize Cache page for anyone who experiences the same issue with this plugin.