Ben
Forum Replies Created
-
Another site in the multisite managed to go pass the “Preparing publication” status, but got stuck at “Deployment initiated (*** results total, ** results deployable).”
Forum: Plugins
In reply to: [Staatic - Static Site Generator] Page Not Found Path: /404_not_found/thanks for the amazing support!
Forum: Plugins
In reply to: [Staatic - Static Site Generator] Page Not Found Path: /404_not_found/Thanks. I have sent the requested info.
Forum: Plugins
In reply to: [Staatic - Static Site Generator] Adding custom code to .htaccessAlternatively, maybe you can provide these options in the GUI:
- Redirect non-www URL to www URL and vice versa
- Compress components with gzip
- Add Expires headers
Forum: Plugins
In reply to: [Staatic - Static Site Generator] Adding custom code to .htaccessThanks! It works as expected. It would be great if there is textarea for user to input via GUI instead of via functions.php
Forum: Plugins
In reply to: [Staatic - Static Site Generator] Configuration Issuesthanks again for the fast reply.
Own server IP restriction is set in .htaccess, php settings or other location in Cpanel?
Anyway, after I reported this, I enabled HTTP Authentication for the website and set the username and password in Staatic Settings (Advanced) and the error is gone.
Then I initiated Publish. I managed to crawl over 2,000 resources until it hits this error…
Error during task Staatic\WordPress\Publication\Task\CrawlTask: The path of a URI without an authority must not start with two slashes "//"
Forum: Plugins
In reply to: [Staatic - Static Site Generator] Error when save changes in Deployment tabyes. that’s fixed it. thanks!
Forum: Plugins
In reply to: [Raw HTML] [Plugin: Raw HTML] Conflicts with HTML commentsSame problem here.
create an empty php.ini file and put in this line…
safe_mode = Off
upload it to your public_html folder. after that, add this line in your .htaccess file…
suPHP_ConfigPath /PATH/TO/public_html
of course edit the above line to match your path to your public_html folder.
It works for me.
Yes, you are right. There is additional </div> at line #200 in /app/view/calendar.php
I have removed that and it is OK.