Rune Rasmussen

It’s obvious we can’t agree on this, sitting on different sides of the table, where you as a plugin developer is defending the use. Thus it could be useful with someone representing WordPress and the users voicing in also.

But …

1. When someone does something to someone or something that they aren’t supposed to, it’s abusive in my world. They are taking advantage of the situation and/or system, in this case it’s a system abuse. But I’m really not here to discuss language understanding, and I think honestly most understand well what I mean when I use this wording.
   
   Anyhow in other settings the guidelines are actually being read as if they read ‘must not’, instead of ‘should not’, and it’s not up for discussion – so it becomes a bit confusing for everyone in the end.
2. Sure it’s volunteers, so is it in other projects, but that doesn’t mean they allow it to be anarchistic, letting plugin developers do whatever they like.
3. ‘Lively hoods’ and ‘Livelyhood’ has quite different meanings, so thanks for clearing up that you meant ‘Livelyhood’.
   
   I can fully understand that some plugin developers maybe want or needs to make a living from plugin development, but if they need to take advantage of weeks guidelines and system abuse to display adds around in the system where they shouldn’t they might have to reconsider a bit.
   
   Honestly I think most serious (GPL) projects doesn’t allow this kind of system abuse to up sell etc., newer seen it being done like this anywhere else. Those projects would probably not allow the listing of such a pluging, and if it’s added later they would most likely unpublish it and notify the developer, requesting them to fix it before republishing. Then if added again later on they might warn and ban for some time, eventually permanent if it happens a lot.
   
   Because it’s after all intrusive and harmful for the project itself, it’s annoying, and it gives the project a bad reputation – not only the plugin and plugin developer itself.
   
   And then again, as I wrote in the first post, they also creates accidents, and then you might have some serious issues created from this system abuse and bad UX:
   > but “recently” some also have started including Install buttons in their ads, which has lead to admins accidentally installing plugins they don’t need.
   
   * Pushing a install button like this might t.ex. happen easily in WP admin because of all the unexpected layout shifts (ref CLS) going on.

In my opinion there is no use in having guidelines and rules, if nobody cares about them, and there’s nobody to ensure they are being followed. But thanks for the link, it can be useful.

As it seems these days there are more and more plugins abusing the notification area for direct marketing etc., what they do has nothing to do with notices related to the use of admin – it’s pure ads and spam.

Asking the users to take the dialog with the plugin devs is a bit backward, and I hardly see that those devs will care if one or two users contacts them, to ask them to follow the guidelines.

Asking the users to install yet another plugin to deal with flaws in WP is just harmful to the project, nor is there any plugins who is able to handle all the various variants of ads and spam added to the notice field (already tested before posting the tread).

asking them to make subjective decisions on plugin developer lively hoods.

Not sure what you’re saying here, I don’t know the term ‘lively hoods’. But we know that Joomla and other projects are able to handle abusive and risky plugins quite nicely, unpublishing the plugins and contacting the devs to force a change.

The WP Feature Notifications project seems anyhow interesting though.

• This reply was modified 1 year, 2 months ago by Rune Rasmussen.
• This reply was modified 1 year, 2 months ago by Rune Rasmussen.

And now also here https://github.com/woocommerce/woocommerce/issues/37761

Also here: https://github.com/woocommerce/woocommerce/issues/37750

See https://github.com/woocommerce/woocommerce/issues/37750

There’s a link to a screen recording of the issue also.

And some more screen recordings etc here: https://www.ads-software.com/support/topic/product-attributes-disappear-in-wocommerce-7-6-0/

• This reply was modified 1 year, 7 months ago by Rune Rasmussen.
• This reply was modified 1 year, 7 months ago by Rune Rasmussen.

Oh, the link in the plugin takes me to a test form?

Try it!
This contact form will send an e-mail to you instead of me (so that you can test it).

Of course there is plugins, not many running stock WP/WC.

And I also thought one of the points of this plugin was to identify and making it possible to remove leftovers, but if we need to do all that research on where the tables are coming from, it looses some of its point.

Bought the Pro also, it reduced the unknowns to 33. One of the Redirects tables (_WP_SEO) being recognised, rest not.

there is a section for that in the Settings

OK, there seems to be a section generating a list that needs to be Submitted through a form on your site. Wasn’t exactly what I had in mind when thinking easy, but OK, it helps somewhat.

you can associate tables with which plugins they are used

If the plugin is already removed, and this actually is some unused table it seems like it’s not possible (also no way to mark tables as not used, for later ref)?

Thanks. ??

LOL… One month and one week later …

I’ve removed XCloner from all sites. As I said, I don’t have time for debugging it, or checking all related pages.

This should be enough for you to start with:

also the WP Dashboard because of the Woo widgets there.

Anyhow, I’m out. So don’t expect any updates from me, I’m signing out of this topic. ??

Sure, as stated, inside the backup folder.

Like
/wp-content/backups-GgoVN/.xcloner
/wp-content/backups-GgoVN/.xcloner6416

Sorry, but no. I have already removed XCloner on all sites, as it’s to unstable, but I’m pretty sure you can see it for yourself in any test environment, as it has been like that in all sites (using local storage).

Folders are named .xcloner and some random digits, so it should also be possible to find the creation of them in the code.

My guess would be that they are from all the failed scheduled backups etc, which is also why we can’t trust and use XCloner anymore.

However, anyone got a php solution for this?

It’s being added in /wp-content/themes/neve/header-footer-grid/Core/Builder/Footer.php by the add_footer_component function and the add_action above:

add_action( 'neve_after_slot_component', [ $this, 'add_footer_component' ], 10, 3 );

So a remove_action snippet should probably do it.

Is that really so? That sneaky added footer text and link doesn’t have it’s own CSS classes. ??

Hi,

I had it installed on one simple site with almost no media, so I updated it there. Then I added a schedule to it, which was showing executed after the scheduled time was passed, but still there was no backups taken, and no error or log. Only notification found is about there being no backups.

Manual backup did work this time though. ??

Thanks, seems to works nicely now.

*Had some summer vacation, thus the late reply. ??

Thanks for the history lesson, but you’re not the only one being around since Mambo. And also Xcloner have been around for some time, for Joomla also previously. ??

As I said it’s good for you if it’s works for you, but that’s not the case for everyone else at all time as we can see around.

Some of the missing parts in Xcloner has already been mentioned, and the owner of Xcloner who is Watchful, knows what’s missing at that end.

It’s been stated several months ago that a new version is coming soon. Don’t know what soon is if it’s 4-5+ months ago …

Anyhow, this isn’t leading anywhere.