Darken-x

Thanks for the feedback. The plugin will be updated soon to cover the latest WP changes. Cheers!

5.1.0

Luckily, no. A quick fix was to downgrade the ShopWP version, so it’s quite certain the error is from ShopWP and not from Shopify API or any other parts of the website (plugins, WP version, theme etc.).

Yup, same here (on https://www.hop-kettle.com/ )

A quick fix was to downgrade the ShopWP version, so it’s quite certain the error is from ShopWP and not from Shopify or any other parts of the website (plugins, WP version, theme etc.).

• This reply was modified 2 years, 5 months ago by Darken-x.

I have the exact same problem. Tested with nearly 10 CTX Feed updates/versions back, but the problem is there regardless of plugin version.

The only “solution” I could find somewhat usable is to make only one change at a time, then save, then edit again. For example, adding a new attribute is done in 2 steps: first you add the attribute, leave it as the last line item, save, then edit and move the new attribute to the desired location, save again. Doing more than one change in one go, then saving, created errors – you’ll get some of your attributes removed, others saved, others misplaced.

Happy you liked it!

• This reply was modified 4 years, 7 months ago by Darken-x.

Can confirm there is indeed a bug. On Firefox the behaviour is exactly as described above, plus the fact that you get an unusable Bold Builder box underneath the desciption, with an additional error that disables javascript on the page.

Clearly a bug.

Did not notice problems on Chrome though.

Thanks a lot for the feedback. I also recently noticed the pink-ish shadow issue with Woo’s notifications. Will fix shortly. When time permits, I will expand the compatibility with the major plugins. So far, the latest version covered ACF and Classic Editor. And WooCommerce, if you disregard that alert box ‘bug’.

Much appreciated!

Hi and thanks for the feedback.
Normally the oldstyle.css only gets applied if you are logged in as admin and only to the admin interface.

Are you describing a situation where you get the restyling of input[type=”text”] on the frontend as well? (assuming you are already logged in as admin, that is you are able to see the admin top bar on the frontend)

You’re most welcome <3. I will put up an update tonight that also extends this old style UI to Gutenberg and adds compatibility with other common editors, plus with the latest Advanced Custom Fields CSS update.

The 5.3 changes are documented in the WordPress release, so anyone interested in why they were made can easily view them there. There is no point in reiterating them here.

The fact that you rated the plugin 1 star out of spite, and for reasons other than those that are normally meaningful when rating a plugin, does not help anyone.

I believe everyone should be able to choose how they style their interface.

And moreover, nobody challenges the website accessibility requirements and their benefits – yes, they are needed. The method and result are however questioned. There are far better ways to achieve accessibility other than the multitude of dark lines and thick borders.

Thanks a lot for finding and fixing this warning!

I’ve updated the plugin to reflect this.

Cheers!

Thanks!

Hope you’ll find it useful.

Hi,

That is actually a very good idea – adding an option to activate/deactivate the Dublin Core metadata on specific pages or custom types.

I will consider it for the next development stage.

Cheers!

Hi,

What kind of meta data do you actually need?

Or was that just an excuse to post your link?

Cheers!