patrickposner
Forum Replies Created
-
Forum: Plugins
In reply to: [Simply Static - The Static Site Generator] UTF-8 converted to HTML entitiesHey @mlanners,
I’ll give this a test and follow up!
Update:
I just gave this a test and it exported just fine (without any UTF-8 conversion):<div class="entry-content alignwide wp-block-post-content has-global-padding is-layout-constrained wp-block-post-content-is-layout-constrained">
<p>KommunizΓ©ieren mat Luxchat</p>
</div>Are you running on the latest version of Simply Static?
- This reply was modified 7 months, 4 weeks ago by patrickposner.
Forum: Plugins
In reply to: [Simply Static - The Static Site Generator] Nothing at allHey @mooball,
thanks for reaching out!
This is most likely something related to your server – we often have that if people try to run it on really cheap (and often unmaintained) servers where the problem is caused even before WP is loaded (on the Linux-level).
A couple of things I would check before looking further on the server-level:
- is WP up-to-date?
- Are you blocking the WP Rest API with some plugin?
- Any bulky security plugins enabled (like WordFence?)
- What about the PHP version? 8+ already?
- Have you enabled the Debugging Mode?
- Any badly-configured caching plugins (Litespeed?) running?
This should give you a good starting point for debugging.
Hey @drcq,
thanks for reaching out!
I would first look at the permissions for the wp-content directory.
It’s really CSS and PNG files (what about JPEG and JS files, do these get copied just fine?).
Are you already using the Enhanced Crawl feature?Forum: Plugins
In reply to: [Simply Static - The Static Site Generator] Error… Maximum execution timeHey @reiner1957,
thanks for reaching out.
Given the number of pages and files, your server (or local computer) might not have enough power to run the ZIP task (that’s why it causes the timeout).
If you only want to use it for archival reasons, use “Local Directory” instead and zip the result manually to avoid this issue.
same, honestly!
At least from the specs it looks alright, but there is probably a reason why they are so cheap (What is even that distro? Linux? Which Linux? And why is the version over 2 years old? π )
I don’t really think we can help here, it’s just too specific.
I would probably just go with something like Digital Ocean or Hetzner, where I can at least be sure the installed server software is somewhat up to date.
Hey @koto305060,
it’s part of the official 3.4.5 release now! π
Hey @koto305060,
thanks for the additional information!
We are probably able to debug that without seeing the actual site – I simply used your example:
γ’γγ€γ« β モバイルAnd was able to replicate it!
I’ve added a patch for that now: https://github.com/Simply-Static/simply-static/commit/593e10d19bf9135afc1b74f6d8a9ebed849fa5d5
We still need to run a couple of tests to ensure it works for everyone before we can release it (as it is a significant change), but it has solved the problem for the given example.Hey @dmitryzan,
we don’t typically provide that level of support in the forum, and there is a reason why our REST API is marked for internal use only and not exposed via the documentation.
I don’t want to go into too much detail here (again, out of scope), but you’ve probably missed some critical parts in your code:
function ss_run_export() {
// Get the current blog ID.
$blog_id = get_current_blog_id();
// Important to support integrations.
do_action( 'ss_before_static_export', $blog_id, 'export' );
// Clear transients.
Simply_Static\Util::clear_transients();
// Immediately run the export.
Simply_Static\Plugin::instance()->get_archive_creation_job()->start( $blog_id, 'export' );
}By using the “start” method, you trigger the export immediately, whereas “run_static_export” always defaults to CRON first if available.
Hey @koto305060,
thanks for the report!
Can you share the URL of your (static) site with me here?
I would love to extract the content and run a couple of tests to see why this might happen.It’s definitely not the expected behaviour – we only do that for HTML attributes (CSS classes, etc.), but we should not convert the entire text.
There might be an easy way to handle that with a filter, so once I have some test examples, I’ll take a look and keep you updated on the progress!
Hey @tremlas, thanks for the confirmation and the great review – much appreciated! π
On to the next 5 years! πͺ@fabiocchetti do you have the WP debug log enabled? There might be a notice indicating what happened – perhaps it’s a conflict with another plugin (unlikely), or maybe there’s not enough memory on the machine (265 M should be the minimum).
@tremlas Alright, it’s finally fixed now (the last approach indeed not fixed it π ).
We will ship the fix in the update tomorrow!Hey @vertigo98,
thanks for reaching out.
The fix for this will ship in tomorrows update.
In all honesty, I’m this close to making Elementor support pro-only soon. The amount of time we have to spend to fix broken Elementor code and find workarounds for all the stuff inside Elementor breaking WordPress conventions (CSS, JS, and font files in wp-content/uploads, no proper MIME-types for files, huge memory issues with their bundler, hardcoded URLs in JS) costs us hundreds of hours each year.
I’m not sure why we should bother with that anymore within the free plugin.
@tremlas ah, good catch!
I’ve added another rule to both crawlers now to specifically check the CSS files for inline references: https://github.com/Simply-Static/simply-static/commit/fb8c46f69a28acb7cb6a77b9ccd01bcbb7282a31
If you feel adventurous, you can simply copy and paste the changed into both files and give it a test!Hey @acp693,
thanks for the follow-up!
We never added specific multilingual support into the free plugin; it just happened to work just fine with Polylang π – the integration was needed for WPML and TranslatePress.
We won’t restrict the old crawling mechanism (this one will still pick up both languages just fine), but we won’t add explicit multilingual support for the new Enhanced Crawl feature to the free plugin.