urkvmdr

Hello,

I agree that plugins need to update their code when WP changes are implemented. However I don’t agree with your reasoning.

Being a software developer for nearly 40 years and currently developing mobile apps for iOS/Android, I think the situation should be slightly different.

Following how companies like Apple approach this situation where both third party libraries and mobile apps are depending on the iOS version. Apple never implements breaking changes just like that = changes where libraries of mobile apps need to update their code, without first keeping the code backward compatible and warning developers of upcoming breaking changes by warning them during building code that the current code used by the library or mobile app (in your case the plugin) is being deprecated. So for a limited time both the old implementations and new updated code will work. During the grace period iOS will only have minor version update e.g. as in your case 6.7.2 to 6.8 is a minor version update and should not break dependent code of others.

At a certain moment Apple decides the developers had enough time and they will release a major version upgrade and then non complaint code will break, but developers can decide to keep running the old code. Of course those developers of libraries block me as developer to upgrade to the latest iOS version, but then I can decide to choose another library or contact the developer of the library to update their code. In your case the version should have been going from 6.7.2 to 7.0.0 as it breaks code.

So I am not saying your WP code breaks, but I don’t think it’s proper citizenship a feel you surprised other developers with breaking changes which become apparent for websites that reply on the software cycles of WP and plugins to be aligned.

Of course I will notify the developers of plugins affected about the issue and hope the fix their code. Until that time I probably downgrade WP to 6.7.2 as long as I feel that seems safe.

Now finally having two editors installed is hardly uncommon and has basically nothing to do with the problem I reported. The issue doesn’t occur if Elementor Pro is activated. It happens if other plugins are activated that are not editors, but just want to add stuff like SEO information (index yes/no), set a permission.

In some case it’s convenient to use the standard editor for small changes. If the editors behave correctly they should be able to coexist and in my experience after years of working with Elementor the issue is not related to multiple editors as the issue also occurs for content created with standard editor.

NOTE: please ignore the remark regarding the ‘Vast bedrag’ = [paytium_field type=”open” label=”Open bedrag, incl 21% BTW” amount=”25″ tax=”21″ /]

That one works fine, I didn’t see the field to fill-in the quantity at first as it was on the far right and shifted a bit due to alignment of fields.

So I am only stuck with limit problem

I checked another web browser (Firefox), same issue.

I just don’t get a field to enter the number I want to order. The form is doing calculations as it show a total as if the number entered was 1. My amount is set to 25, total is also 25.

With the ‘Vast bedrag’ line I see a QUANTITY=TRUE which suggests a field will be shown to enter a number. That QUANTITY is missing and doesn’t work for the limit case.

P.s. I really tried your suggestion and different quotes, but no luck.

So I hope you see something or think of something. Especially as the example code when copied 1-1 gives problems.

Thanks, Bart