dirkd

Hi @dimitrycleantalk

Yes, I ment the security plugin of course and mentioned the anti-spam version number by mistake. I did what you asked. Reinstalled the security plugin (2.112) but it did not help.
So, I started to deactivate all my plugins one by one and found the culprit.

There was a plugin named ‘Remove category URL’ that I am using for many years now. It simply removes the word  ‘/category’ from the category permalinks.

Since updating to version 2.112 of your security plugin this plugin is now causing the 404 error.

I found an alternative solution by changing the permalink structure to /%category%/%postname%/ and replace the category base with a dot.
I did not realize that the plugin was not necessary anymore.

Anyway, all fine now ??

• This reply was modified 1 year, 8 months ago by dirkd.

Good morning @rilwis ,

Yes, that’s exactly my thought too. ‘Translate’ makes the most sense here.
When I copy an article to another language it takes over the Meta description but this time I can edit it correctly in the other languages.

Hi @rilwis , I received a reply from Polylang with the solution.

It seems the ‘Custom fields‘ checkbox under the Polylang settings in Languages > Settings > Synchronization has to be unchecked because the Meta description is stored as a custom field. In my case it always overwrote the descriptions for the other languages with the last one that I was editing.

So, the issue is solved!

They also mentioned that you – as the author of Slim SEO – can check their doc for a finer control of the multilingual behavior of the custom fields:?https://polylang.pro/doc/the-wpml-config-xml-file/
Configuring this file would help you to control the behavior of the custom fields as well as multilingual options in both WPML and Polylang/Polylang Pro.

Thanks!

• This reply was modified 1 year, 9 months ago by dirkd.

Hi, thank you for replying. OK, I will try to contact their support and see where this is going …

I can confirm that the error “Maximum call stack size exceeded …” is fixed after downloading the update mentioned above (Github link).

So, currently I am on version n° 5.154.1

BUT … another problem came up. Now the SAVE button in Oxygen does not work anymore. It is impossible to save edits because nothing happens when clicking the blue SAVE button.
So, I started to deactivate all plugins. SAVE button worked again!
I then reactivated my plugins one by one and found out that it is Cleantalk that is causing the problem. For some reason it disables the save function.

Latest versions :
WP 5.7
Oxygen 3.7.1

I have to disable Cleantalk until you find a fix for this.

Thanks for any feedback on this.

I also had to roll back to older version. Client complained when checking on smartphone. When I saw the results on smartphone it was even worse.

The old version’s shrinking effect is also a lot smoother. Really a big difference in smoothness.

So, also rolled back. Hoping for a better update soon.
Best regards. Dirk

• This reply was modified 4 years, 5 months ago by dirkd.

Another update:

When I added your CSS the issues seem to be solved for Safari and Chrome but NOT for Firefox. In FF the page is still pushed down when negative margins are not used.
I will keep testing further on my other websites and let you know when other problems appear ??

.logged-in .she-header {
top: 0 !important
}

OK, I have a second site with your plugin. It seems the issue is NOT solved.
I tested in three browsers (latest versions). There is weird behavior in all of them. Here’s what I am experiencing now with 1.4.1.

1. Firefox :
When loading the page, the page content is pushed down. The header section appears above the page. I am not using negative margins.
When I start to scroll everything suddenly appears normal. The header section looks normal and loads over the page (transparant).
Until I reload the page… the header section again shows above the page content.

2. Safari
Here the header shows correctly, transparant like it should be.
But when I start to scroll the margin above the shrinked header is back. Like in the screenshot that I posted earlier. The problem returned with version 1.4.1. Clearing caches on server and browsers does not fix it anymore.

3. Chrome
Same issues as with Firefox.

When I use negative margins again for my page hero sections, the problem is solved in Firefox and Chrome. All fine again with the negative margins active.
But NOT in Safari. Here the margin above the shrinked header is always visible after scrolling (like in my screenshot)

I hope this helps to identify the problem. Thanks a lot for your help !

Live website : https://www.kapperludo.com

I think I can confirm this on my staging site. Plugin has been working perfectly… till the last update. Suddenly I see a margin appear above the shrinked header.
Look at screenshot to see what I mean. Site is not live yet, so can’t share URL.

https://pasteboard.co/JrO8G0a.png

(update: problem solved. The problem showed up only in Chrome. Safari and Firefox were fine. After clearing the browser caches it was solved)
??

• This reply was modified 4 years, 5 months ago by dirkd.
• This reply was modified 4 years, 5 months ago by dirkd.

Hi, several months and another update further (version 3.0.3), and still no solution … ??

Field still do not appear in cart/checkout/e-mails!
Can you please let me know how to proceed in Avada ?

@azaozz Yes, I saw the JS source.
But, I can inform you now that it mysteriously works again.
I uninstalled the plugin. Then emptied the SG cache and cleaned up the database.
Reinstalled the plugin and noticed the error disappeared.
Don’t really know what caused the issue. But I’m glad it’s working normally again.
Thanks for the good feedback here ! ??

@azaozz,
Cannot get rid of the error. Have to stick to 4.7.11 or use another browser (which I don’t prefer). Any ideas how to solve it ?

Oh sorry. Didn’t realize this. Anyway, problem is solved, so thank you ??

Hello Andrew,

– Chrome Incognito screen has no effect. Error still present.
– Removed all my browser extensions : no effect
– Opened [site.url]/wp-content/plugins/tinymce-advanced/mce/nonbreaking/plugin.min.js : no errors in the console

But then I deleted TinyMCE Advanced and reinstalled the previous version 4.7.11. Now the error is gone, just as Renato already wrote above.
Maybe this might help you to find out what is causing the issue in 4.8.0 ?

I’m afraid I have to confirm this. The error message also showed up here.

However, I tested on several systems and found out the error only appears in the Chrome browser on my iMac. No problem with Safari and Firefox !
The weird thing is that there is also NO problem on Chrome on my MacBook Pro.

So, it seems iMac related and Chrome only.

Reinstalling WP + deleting and reinstalling TinyMCE Advanced also did not work.

@schirmer_rs, @gotmedia, can you confirm you are working on iMac also ?

• This reply was modified 6 years, 4 months ago by dirkd.
• This reply was modified 6 years, 4 months ago by dirkd.