mussy
Forum Replies Created
-
Forum: Plugins
In reply to: [Visualizer: Tables and Charts Manager for WordPress] Broken after updateHi, when I added the new chart in Firefox it seemed to fix it all in Chrome. Think there must have been something corrupting one of their tables.
Forum: Plugins
In reply to: [Visualizer: Tables and Charts Manager for WordPress] Broken after updateNote: this was in Chrome.
Tried on Firefox and managed to add a new Table which somehow brought the page back to life.
It’s okay, got on in the end.
Forum: Plugins
In reply to: [Contact Form 7] ReCaptcha V3 breaks form on IE & EdgeHi, you’re right, just tried it on another site and it worked okay on Edge and IE. Must be something else conflicting with it on that particular site. Thanks for the heads-up.
Forum: Plugins
In reply to: [Contact Form 7] ReCaptcha V3 breaks form on IE & EdgeThanks, didn’t know you could do that. Very helpful.
Hi, thanks for the response.
I tried asking a pre-sales question but it won’t let me because I’m already registered. When I click on the suggested link to the technical support forum, I’m told it’s no longer active and there’s no option to post a new item or ask a question, so not sure how I can ask a pre-sale question other than here, so here it is:
Types is already a very large plugin (36Mb) – how large is the full Toolset plugin? I wouldn’t use 90% of it so struggling to see the advantage of paying for a full licence.
Does the WYSIWYG field work on the paid version of Toolset?
I have over 100 websites, I can’t replace all these with alternative plugins and re-code every bespoke template I’ve built.
I feel like you’re giving developers like me no option but to move to the paid version. I’m willing to do this, to save giving myself a load of extra work, but I can’t do it without the assurance that the plugin will work when upgraded to the full paid version. Does the WYSIWYG field continue to work as normal on the paid version, when sites are upgraded to Gutenberg?
Further to this. The WYSIWYG field will update if it’s switched to Text mode, but in Visual mode, nothing is saved.
Thanks for the fix. This stops the “blank page” problem when trying to edit a page but there are still issues.
Looks like custom WYSIWYG Types field data isn’t being saved. Tried it on a site where there is an “Additional Info” block containing a single line heading and a WYSIWYG block for text. The heading field updates okays, but the WYSIWYG changes don’t save to the DB.
Also, all formatting in the WYSYWYG boxes gets lost – paragraph breaks etc. aren’t saved.
Same problem here. Console is firing out lots of errors on the white/blank edit page.
First one is:
Uncaught TypeError: Cannot read property ‘extend’ of undefined at backbone.min.js:1Then:
Uncaught TypeError: Cannot read property ‘memoize’ of undefined at wp-util.min.js:1Followed by approx 30 similar errors. Disabling Types makes the edit page load correctly again.
Forum: Plugins
In reply to: [Advanced Booking Calendar] Can only select 1 person on booking formForget this, deleted the Double room – which I’d originally set with max of 1 person, but changed this to 2 after I published it.
Deleted it and started again and it works now.
Looks like the max occupancy field isn’t feeding into the booking form dropdown after its initial setup value though.
Thanks, yes client has reported it’s all fine now. Must have been a caching issue on PC.
Forum: Fixing WordPress
In reply to: WordPress 4.9. Theme php file editing.Thanks, I know that. Problem is when someone tries to edit a theme file direct via WordPress.
I’d always discourage this, but on occasion, it may be necessary. This was flagged up by a client’s SEO company trying to alter their Google tag.
Forum: Plugins
In reply to: [Contact Form 7] Count not working in Mac ChromeWeird, it’s working locally with all plugins and WP updated to the most recent versions, but on the live site – with all plugins & WP updated to the same level, the count remains at zero.
No problem. Did think it would be the format of the dev URL that would be causing the validation error. This is the “out of the box” setup for MAMP though so will affect lots of users. Please advise when a fix is released.