click

@momozizou – please post your issues on a fresh thread, as this is about something totally different.

Hi, any news on corrections/adjustments with regards to role-based purges?

Allowing them to purge any page/post they could edit would be sufficient I think.

Some additional background:
Case 1 is a newspaper-site which has an editorial staff, and where we’ve adviced them to keep the amount of administrators to a minimum. They have lowered the roles for the additional administrators down to an ‘editor’ role.
They would prefer to have access to to a complete purge, however.

Case 2 is related to a client using a “custom roles”-plugin, which incidentally resembles the same issue as case 1 – eg. the site-admin has restricted their clients access to only be able to handle specific tasks via a custom role-based setup.

In both cases it seems to be an issue of granting/restricting access to
– edit/purge the frontpage (or ALL pages)
– edit/purge pages they can edit
– edit/purge articles/posts they can edit

Additional: A colleague of mine commented that this COULD be resolved by adding support for using filters in the plugin.

• This reply was modified 2 years, 4 months ago by click. Reason: Clarification
• This reply was modified 2 years, 4 months ago by click.

Quite a few sites will break/whitespace with PHP8.x simply due to that PHP8 deprecates functionality that a LOT of other plugins and themes use.
With regards to your comment ‘will only get security-fixes’, that is the entire intent of how the devcycle for PHP works:
No new or additional functionality or changes are done to the 7.4 codebase, only security-related updates – it doesn’t mean 7.4 is deprecated.

As per current the list of supported versions are:
– PHP 7.4 mainline support ends 28 Nov 2021 (2 months)
– PHP 7.4 security updates ends 28 Nov 2022 (14 months)
(reference URL: https://www.php.net/supported-versions.php)

I’m not biased here (using PHP8 is good), but enforcing PHP8 like this is a REALLY bad move and will affect a lot of users – you could actually support both untill 7.4 is deprecated with #ifdef-tests and logic.

• This reply was modified 3 years, 6 months ago by click. Reason: text styling

Hei,
du m? dessverre ta kontakt med Vipps AS sin support igjen, og opplyse om at det gjelder tilgang til f?lgende for ditt kundeforhold (de vil sp?rre om din merchant-ID osv) :

“eCommerce Express Checkout with Signup-Login API”
eller
“eCommerce Express Checkout”

Utvidelsen vi har utviklet for Vipps st?tter kun nyeste versjon (versjon 2), og m? bekreftes av de. Informer de om at dette gjelde WooCommerce-installasjon ogs?.
Beklager at vi ikke kan hjelpe deg mer enn dette.