Lea

Hi,

Can you explain to me where the shortcode is? Because all I see is a field in the post editing screen:

Thank you very much for the css fixes. They work.

Regarding the date: what shortcode would that be? I see a field that has the date in it, but I leave it empty, the event doesn’t appear in the timeline at all

Here is the code that worked at my end:

ine no. 587:
wp_enqueue_style( ‘csf’, CTL_PLUGIN_URL. ‘admin/codestar-framework/assets/css/style’. $min .’.css’, array(), self::$version);

line no. 591:
wp_enqueue_style( ‘csf-rtl’, CTL_PLUGIN_URL. ‘admin/codestar-framework/assets/css/style-rtl’. $min .’.css’, array(), self::$version, ‘all’ );

line no. 595:
wp_enqueue_script( ‘csf-plugins’, CTL_PLUGIN_URL. ‘admin/codestar-framework/assets/js/plugins’. $min .’.js’, array(), self::$version, true );

line no. 596:
wp_enqueue_script( ‘csf’, CTL_PLUGIN_URL. ‘admin/codestar-framework/assets/js/main’. $min .’.js’, array( ‘csf-plugins’ ), self::$version, true );

Thank you

OK, that was the problem – the css and js weren’t loading.
I fixed it with the main part of the code you sent (I had to change the apostrophes because they weren’t recognized by my IDE, and the , ‘all’ parameter in the 587 caused an error).
So it turns out that CTL_PLUGIN_URL was the wrong path. Can this be fixed in a future version?

On second check, the upgrade works well, but deactivation doesn’t work. It just leaves the site hanging, and when we refresh, the plugin is still active

OK. There is only this plugin:

OK, I found the culprit. It’s this line in function set_firewall_configs():
if (version_compare($firewall_version, ‘1.0.1’, ‘<‘))
where $firewall_version is assigned the value of get_option(‘aiowpsec_firewall_version’);

We’re on version 5.1.0, where this option doesn’t exist, and when updating to a higher version the get_option apparently returns a value of false. However, version_compare() expects 2 strings, and I assume that when it gets a parameter that’s not a string, that triggers something that causes the 504 error.

I’ve found a workaround for this, so I don’t know of you actually have to fix something in the plugin’s code. I do the following:

1. Download latest plugin version and unzip to a folder
2. I comment out lines 480-494 in all-in-one-wp-security-and-firewall\classes\wp-security-configure-settings.php
3. I upload this folder to the site and activate the plugin.
4. Following this successful upgrade, I uncomment those lines. This is possible due to the fact that line 496 in that file updates the option ‘aiowpsec_firewall_version’.

That’s all ??

Hi,

Do you mean this dashboard?

Hi,

Sure, here it is (I don’t see any errors in it)

Ok, I tried it by uploading the files straight to the /wp-content/plugins folder and thus replacing the older version, but when I refresh the site, I get the 504 error.

Is there a repository from which I can download previous versions? we have version 5.1.0, and I would like to check which is the latest version that install correctly on out sites

• This reply was modified 11 months, 2 weeks ago by Lea.

Thank you for the new version, but installing it creates a “504 “504 Gateway Time-out” error, as I described in another issue, so unfortunately I can’t check the fix ??

We’re updating from version 5.1.0.

The problem with the update has been happening since version 5.1.1, but we only now found the time to ask you to help us solve the problem, sorry.

And here is a link to the pastebin of our export:

https://pastebin.com/DvwPXmka

Renaming didn’t help, we had to rebuild the image.

Also, the site is running on nginx, therefore there is no .htaccess

Since this happens only when updating this plugin, and it happens in more than one site, the article you sent isn’t helpful

• This reply was modified 11 months, 3 weeks ago by Lea.

It took me a long time, but I finally discovered what part of the Duplicate Page plugin interferes with the appearance of the Custom Fields: When the “All Editors” option is chosen in the “Choose Editor” definition, that affects the ACF. I changed it to “Classic Editor” and that solved the problem.

I have no idea why it is thus, but that is my finding.

Thank you for the detailed answer. We will try that the next time we get blocked