Forum Replies Created
-
Posts
-
All good this has been resolved. Wasn’t a conflict after all. Just a column link that shouldn’t have been there. Doh.
Hi Rikard,
It’s actually this form: http://projectcameron-com.stackstaging.com/providerinformation/
It seems to be a conflict between the theme and forminator pro plugin. I have asked WPMU Dev about it also.Hi Nikko,
Thanks for that. Although that was a problem we were aware of we can see it was still not working. However applying your fix has made it easier to see what exactly is going on. If you would be kind enough to take a look again you will see that you still cannot type in the boxes. Well you can if you hold down the mouse button and type. this makes me suspect the input fieldds are losing focus and I can only think it’s a JS thing?
Thanks again
Actually we have changed the url try these:
http://projectcameron-com.stackstaging.com/providerinformation/
Hi Nikko, looks like one of our devs resolved the problem already ! Thanks for looking and apologies for wasting your time.
Hi Nikko,
Thanks so much for that! I had no idea it had been added in as an option.
However, after removing the function code and updating the tab section, the problem somehow still persists!
Hi Victoria,
There was no CSS in the proposed temporary solution as such I have not added any CSS to resolve the problem.
Are there any developers that can confirm whether this issued has actually been addressed and what the problem is?
In the meantime I will put the code back into the functions.php in order to celotape the problem as it has been well over a week and the project is now well overdue.
Cheers
Hi Victoria,
I let the changes be wiped purposely so that the fixes would be applied in the latest version. So are you saying the problem has not been resolved in the latest update?
According to the changelogs it was addressed in 4.0.6
2017 May 16th – Version 4.0.6
– added: functionality for tab_section.php (dynamic content height for tabs)Thanks!
Julian
PS – Do you still need administrative rights or are you just going to edit the functions.php which I am happy to do myself.
As an Avada theme user as well I can assure you the time has not yet come :)
Izevon, what are you patching on WooCommerce? That’s probably something I need to be aware of!
It is a shame I agree but it seems that this is a problem that is affecting all themes that distribute licensed plugins with their theme. Seems to me they need to stop distributing it, still support it for the next twelve months and then still allow integration but stop fully integrating it into the theme.
Would be nice to see the developers wade into the conversation this time though.
Oh really? I didn’t realise. So why has this only just started occurring? I’ve been using Enfold for a number of years and have never encountered this problem prior. A change outside of Kriesi’s control?
Arghh yes back again. Can I make an alarming suggestion, that Layerslider be distributed separately? Not including it in the distribution but providing a separate license would be much preferable although I imagine a bit technically more challenging. I find myself disabling it constantly.
More errors when attempting to upgrade from 4.0.4 but will do an FTP upload later today and report back. Thanks Rikard
Hey Ralf, you are right in respect to the plugin update being related to layerslide, the same issue is affecting everyone I believe, we are still waiting on a fix.
Thanks Vinnie! I’d tried this already but only had one (of many tables) changed to scrollable.
Just to let everyone know, if you have multiple tables, you need to ensure all tables have the same setting or the responsive code still takes a priority for all tables.
Thanks again! :)
Just a little update on this. The form still fails, we’ve also managed to replicate this problem on both an Asus and Samsung Chromebook. It’s really weird. Today we are finally going to replace the form with ninjaforms and see if we can make it look as nice as enfolds (and see if it resolves the problem).
Cleared browser cache across all Chromes and no difference.
Is there any way to troubleshoot, normally I’d right click and inspect the POST data…
Had a few more tests come through from you guys, thanks :)
So weird, still not working on anyone’s office phones. We are using….
Chrome
Android OnePlusOne with Chrome 46.0.2490.76
Android Nexus 5 with Chrome 45.0.2454.94
Android Nexus 4 with Chrome 45.0.2454.85We had a successful test using Android Nexus with Dolphin Browser
