Forum Replies Created

Viewing 15 replies - 16 through 30 (of 910 total)
  • Plugin Author Pieter Bos

    (@senlin)

    The premium menu items hidden with my plugin use CSS, so when you change the order of menu items with the Admin Menu Editor plugin, then that will indeed result in things going off.

    Great that you took the opportunity to try another SEO plugin!

    Closing this ticket now, thanks.

    Plugin Author Pieter Bos

    (@senlin)

    So the issue is the Admin Menu Editor plugin then? Not sure what you need from me at this point?

    I can close this ticket?

    Plugin Author Pieter Bos

    (@senlin)

    Hello,

    Fantastic news and many thanks for your 5-star rating!

    Plugin Author Pieter Bos

    (@senlin)

    you can trigger the update by clicking on the View details link (screenshot)

    Plugin Author Pieter Bos

    (@senlin)

    Thank for the report, I fixed the bug and released a new version already. When you update the plugin to 4.0.2 the Crawl optimization menu becomes visible again.

    Hope that helps!

    Plugin Author Pieter Bos

    (@senlin)

    You have a screenshot or something, because from your description so far I cannot make much sense: “a link hidden” is not very descriptive, what kind of link is hidden?

    Plugin Author Pieter Bos

    (@senlin)

    Hello! Thanks for the review and 5-star rating!

    Funny title ?? Worth the extra plugin you need to install to get rid of the bloat, I guess ??

    Forum: Reviews
    In reply to: [Hide SEO Bloat] Incredible
    Plugin Author Pieter Bos

    (@senlin)

    Many thanks for your 5-star rating and review Hugo, much appreciated! And very happy to hear that you’re happy with the plugin.

    Pieter

    Plugin Author Pieter Bos

    (@senlin)

    Closing this ticket as I haven’t received a response. Feel free to open a Github ticket in case you need to.

    Plugin Author Pieter Bos

    (@senlin)

    Can’t help you without admin access

    Plugin Author Pieter Bos

    (@senlin)

    Well, I’m sorry to say, but that is impossible, unless your host or theme (or other plugin) runs some automated script that installs it.

    I will only be able to help you with this if you give me admin access to one of the sites where this is happening.

    • This reply was modified 1 year ago by Pieter Bos.
    Plugin Author Pieter Bos

    (@senlin)

    The first one will get deactivated automatically when activating my plugin as per my previous answer.

    Looking at the source code of the 2nd one, it should not be deactivated.

    I installed it on a vanilla sandbox and it does not get deactivated.

    Here my screencast that proves that the Classic Editor plugin indeed gets deactivated upon activation of my Classic Editor + plugin. That is expected behaviour as per my explanation, the FAQ I linked to and the source code I linked to. The Classic Widgets plugin however does not become deactivated and will remain activated although it does exactly the same as part of my Classic Editor + plugin, so it is a waste of resources to keep it activated.

    My burning question however is why would you want to install Classic Editor plugin, Classic Widgets plugin and on top of that my Classic Editor + plugin?

    My plugin does everything the other two do and then some. So I would highly recommend making a choice.

    • This reply was modified 1 year ago by Pieter Bos. Reason: add link to screencast
    Plugin Author Pieter Bos

    (@senlin)

    what is the link for the “Classic Editor and Classic Widgets” plugin please?

    Plugin Author Pieter Bos

    (@senlin)

    Okay, now I finally understand. You mentioned Classic Editor and Classic Widgets and I thought that is the name of the plugin that is becoming deactivated. What you meant to say was that you are trying to install the Classic Editor plugin on top of my Classic Editor + plugin.

    If you browse the source of the Classic Editor + plugin, then you can see that it is one file.

    It does deactivate the Classic Editor plugin, as one should not run both plugins at the same time.

    You either choose for the Classic Editor with a settings page, not showing the Classic Editor by default and leaving all Block Editor scripts and styles running on the frontend, OR you install the Classic Editor + plugin, without a settings page, turning the Classic Editor on for all post types and removing the scripts and styles of the Block Editor from the frontend (including those of WooCommerce and WPML if those plugins are active on the site). And last but not least it also brings back the Classic Widgets.

    You can also see from the FAQ that the Classic Editor plugin is automatically deactivated:

    Do I still need the Classic Editor plugin on my site?

    Version 4.0 of the “Classic Editor +” plugin has been a complete rewrite (and simplification) and it is no longer depending on the Classic Editor plugin. When the latter is active, it will be deactivated and then you can safely remove it.

    So you will need to choose my friend. One or the other, not both.

    My tip for a next time you open a support ticket on the WP forums would be to exactly describe your issue. This plugin does not automatically install itself, which is what you claimed.

    Plugin Author Pieter Bos

    (@senlin)

    Send me a screencast of that happening please

Viewing 15 replies - 16 through 30 (of 910 total)