tremlas

@wesleymilan if you need an URGENT fix you’ll need to rollback to version 2.2.7 of the plugin (either by using WP Rollback plugin or downloading (and manually installing) that version directly from https://downloads.www.ads-software.com/plugin/simply-static.2.2.7.zip

(Of course you’ll need to prevent any automatic updates for simply static otherwise it will just get updated back to 2.2.9)

I’ve played about a bit more with version 2.2.8. For me If I press the ‘Generate’ button it initially goes to a spinner but (within a few seconds) the ‘Generate’ button reappears and makes it seem like the generation has failed. However if I then refresh the page using the browser’s refresh function the spinner reappears and it’s clear that the generation is actually proceeding normally, Thus it would seem there’s a flaw in the UI somewhere. In summary my workflow is now to hit the ‘Generate’ button and if/when the spinner disappears I then refresh the page.

I’ve seen the same behaviour on my local site whereby the only way to get the activity log to update is to refresh the page. As a result I’ve rolled back the plugin (using the “WP Rollback” plugin) to 2.2.6.

Updated and this fixes my wpemojiSettings.

I do note from the diff’s of the resulting statically pages that Simply Static now deletes the line break following a script tag (and from the corresponding end tag) – that doesn’t break the resulting page (at least for my use case) but is a change on the output page.

In any event thanks for the update!

I can do a test on my site if you would like a level of system test on the next version – I’ll be staying on 2.1.5.6 until then ??

Just to confirm that 2.1.5.4 fixes this problem.

I had the same problem after upgrading to Ubuntu 20.04. Turns out there’s a dependency inside Simply Static on PHP 7.2 – it does not work with PHP 7.3 or 7.4 (which is the default level of PHP on Ubuntu 20.04). I suspect (but have not tried) that if you change your PHP level to 7.2 the plugin will work fine. Of course changing the PHP level requires access to the host operating system…

For those needing a bit more technical detail, Simply Static includes a library called PhpSimpleHtmlDom. The version (1.5) included in the current version of Simply Static does not work on PHP 7.3.

On my own system I hacked the plugin to include a newer version of the library (from https://github.com/caophihung94/php-simple-html-dom-parser) and this fixes the problem. Obviously this is not something I would recommend unless you have full access to the system and are very happy to hack around the plugin’s code (Also obviously, doing so quite rightly upsets Wordfence).

To avoid this it needs to check if the get_current_screen function actually exists since it isn’t defined in all contexts (theme customization is the main one). So in my copy I’ve updated line 75 to:

if ( is_admin() && function_exists('get_current_screen') && get_current_screen() && 'nav-menus' == get_current_screen()->base ) {

and line 94 to

if ( is_admin() && $query->is_main_query() && function_exists('get_current_screen') && 'nav-menus' == get_current_screen()->base ) {

I could get the menu on moible to appear by adding the following to my child theme – However this will only get the top-level of the menu to display – the submenus will only display on displays claiming to be wider than 1000 pixels.

@media screen and (max-width: 1000px) {
#topnav ul { display: inherit; }
#topnav > ul { display: none; }
}
@media screen and (max-width: 760px) {
#topnav ul { display: inherit; }
#topnav > ul { display: none; }
}

(I believe the problem for the top-menus is that style.css for ming uses a selector of #topnav ul for the tablet/mobile version to suppress the menu by default, which ends up being applied to all levels of the menu, instead of just the top level, so when the toggle enables the top level, all the rest of the menu (including the elements) ends up with display:none) – the above seems to work for me anyway).