Rune Rasmussen

I find it a bit strange you’re using Akeeba on Joomla, and then Xcloner on WP, without missing anything, as they’re quite different in functionality etc. Anyhow it’s not just about a confusing UI, it’s missing some basic and expected functionality – especially against Watchful. And anyhow it’s quite problematic that backup fails doing what it should on like 30% of the sites where it has been installed.

And then there is the fact it hasn’t been updated for more than a year, who alone is a bit concerning.

Well, good for you then @duanemitchell, and I’m sure it works somewhat on small simple sites etc. But the tings mentioned isn’t minor issues to me, and when coming from Akeeba it’s lacking quite much in functionality, also against the owners own Watchful(huh?). So I’ll recommend giving Akeeba a spin to see what you have missed out on, myself I just went back as I need the backups to run when the shall – also manually with one click when needed. Seems like a bad idea to wait for new releases here, coming soon clearly isn’t soon. ??

Works nicely, thanks. ??

Thanks, but wouldn’t it have been more fair and made more sense to add it as a global setting (admin.php?page=metaslider-settings), instead of “hiding” it away?

Just my 5 cents … ??

• This reply was modified 2 years, 7 months ago by Rune Rasmussen.

Actually that doesn’t work as expected, as it also removes the menu items etc.

And from what I can tell the code doesn’t add possibilities for removing it with a simple snippet, but please tell me how to do it if I’m wrong …

Found it, but would still be nice to have a setting for it … ??

Snippet or mu-plugin:
add_filter( 'metaslider_capability', '__return_false');

This will likely be available in a couple of weeks and I’ll report back here to let you know when that is available.

We’re more people eagerly waiting for this one several months later. ??

Thanks,

I just tested it, and from what I can see it has been fixed in 2.13.1

I’m not talking about invoices here, but the display of the buttons for Processing orders who have not been handled in any other way than being placed by the customer, and updated to processing by the payment plugin.

OK, I’ll send you a mail as soon as I get time for it.

But regarding the free version, and anyway what we see, is it intentional that the disable setting etc. isn’t applying to already placed orders? All settings and general behaviour in the plugin only applies for new orders?

T.ex. if I placed an order when 2.13.0 was installed, the button displayed, and it still displayed on the old order after downgrading to 2.12.1. BUT it’s hidden for new orders placed with 2.12.1 active. That part didn’t make sense to me, and it’s also important to be aware of when testing.

One more test; Now adding a new order when having WooCommerce PDF Invoices & Packing Slips Professional 2.11.0 disabled, running only WooCommerce PDF Invoices & Packing Slips 2.13.0 – and it also works as intended.

So it seems like a conflict between 2.13.0 and the Pro version too me.

Tested adding new orders after reverting back to 2.12.1, and the action button for invoice etc. is being hidden as it should.

Then tested adding new order using 2.13.0, and the action button was back.

No settings changed or re-stored in between.

Sure, where do you want me to send the pictures?

Anyhow I tested upgrading WP and Woo, no change.
Then I tried reverting back to 2.12.1, no change.
Updated to 2.13.0 again, no change.
Then I tried selecting the ‘Always use most current settings’, and boom, it suddenly disabled the action buttons etc.

Note! Probably should have mentioned it earlier, but WooCommerce PDF Invoices & Packing Slips Professional 2.11.0 is installed too, and I see no update for it. Nor does it change anything if I disable it …

Yes, as stated it did work nicely before the update. No settings was changed, and they have no invoice no. Processing orders shouldn’t be invoiced after all, they are not at that stage, and that’s exactly why we use the ‘Disable for’.

Only thing changed on the site between working and not working was the update from 2.12.1 to 2.13.0

Haven’t seen anyone being able to use ATUM fully without any premiums yet, so I consider it to be quite commercial, even if it’s made so that it will pass the listing requirements. And indeed we’re free to translate or not, but plugin authors would probably get more translations and paying users if they offered the translators anything for the huge work it is. But enough about that. ??

Anyway, we are going to investigate why that string you mentioned is being overridden by ATUM. Thanks for letting us know about it.
If it isn’t necessary to be overridden we’ll fix it asap ??

Excellent, thanks. ??

Best regards,
Rune