paullacey

Thank for the fix… I know it’s not solved everyone’s issues as yet, but in my case the sql error alert is now gone, and the automatic translations option is able to be activated.

Same problem here…

1
last_error_insert_original_slugs	Table 'appPigeon_1642682813.pigeon_trp_slug_original' doesn't exist
message	Error inserting original slugs.
disable_automatic_translations	Yes
last_query	INSERT IGNORE INTO pigeon_trp_slug_original (original, type) VALUES ('product-category', 'taxonomy'), ('product-tag', 'taxonomy'), ('product', 'post-type-base'), ('uncategorized', 'term')
date_time	2024-08-22 15:32:22
timestamp	1724340742

Wow that was fast. Yes, whatever you patched for Divi… patched it for Beaver Builder and SEO Press too.
Thanks

Just for extra context…

The issue ith SEOPress can be partially resolved by turning off the front end SEO metabox editor.
And the issue with Beaver Builder is when editing on the front end with Beaver Builder…

So it seems that it’s anything that is sort of front end editing modes combined with Modula Gallery installed.

Thanks in advance

Hi Norm,

Looks like you have the samre issue as I had:
https://www.ads-software.com/support/topic/code-syntax-highlighting-field-is-stripping-html-tags/

Thankfully, looks like the team are fixing it but seems like it also needs fixing on the TinyMCE field too.

I’m hoping that any things like this where new filters are being applied but have options, by default are set to being the “as they were” status before new filters and options exist.

Cheers
Paul

Thanks Scott – you are a true star.

Hi there ??

I don’t see an option to allow html tags in the field setup:

https://share.cleanshot.com/8tktRvP4
Note that this screenshot is from rolled back 3.0.10 so perhaps you have added new allow html tags in latest version? If so perhaps legacy fields should have whatever the equivalent would be as default?

In case you mean in the shortcode though, the shortcode I am using is Beaver Builder pods addon (Berhard G):

[wpbb post:pods_display field=’beacon_code’]

Hope that helps solve an issue if there was one.
Seems that it was fine up to and including to 3.0.10.
So my assumption is it’s related to some security things you have added.

Thanks mate ??
Paul

Excellent – great job!
Thank you for a really great plugin.

hi There Michael,

Just to let you know I have this problem too.
Note that I rolled back WordPress core to 5.5
And then the problem goes away.

I tested this with no plugins active other than Classic Editor and CPTUI

Hope that helps.

Cheers
Paul

It’s now working with the update.
Resolved I think ??

Great job! Thanks

Cool – what email address should I send this too?

Hi there,

1.7.2 for the Gravity Forms Source add-on
And 1.4.5 currently for the main plugin.

Hey if it will help, you are welcome to admin login.

Cheers

Yes – because I am running 1.4.5
If I upgrade to the latest version of the plugin, it will stop working.
Right now I’m working with 1.4.5 (because I need to progress project).
So for now, personally I am OK, but I believe there is a problem between 1.4.5 – 1.4.10 for me when I upgrade, and perhaps other users.

Hope that helps ??

And – thank you!
Also, thank you for awesome plugin.

Hi there,

No there wasn’t any caching. There was memcache but I turned it off just now and no change.
However, I have discovered something.

If I roll back to MaxiCharts 1.4.5 everything works fine. Upgrade to latest, then it doesn’t work again…roll back… works… roll forward, doesn’t work.

So it seems perhaps there is something between 1.4.5 and 1.4.10 that stops this working in some circumstances.

If you have the other version (only 1.4.5 is available in this repo), I can try up to 1.4.9 and see where it stopped working ??

Cheers
Paul

Hi @maxicharts

Many thanks ??

Here is the shortcode:

[gfchartsreports gf_entry_id=”{entry_id}”? gf_form_id=”2″ height=”500px” group_fields=”1″ count_answers=”1″ include=”1,2,3,4,5″ type=”radar” chart_js_options=”legend: {display: false} ,scale: { ticks: { beginAtZero: true,max: 30 } }”]

And here is the page:
https://fwcsa.wpcreative.io/short-form/

I have re-activated entry saving on the Gravity Form so that it’s able to re-produce the problem. Note that you will see it work the first time, then go back and try with different numbers and the chart will always use the first entry it finds in the database.

Cheers!