Forum Replies Created
-
Author
-
April 11, 2018 at 18:13 in reply to: I’ve reported a bug to Themepunch/Essential Grid and they won’t look at the bug unless I have the newest version of Essential Grid #194428peterhsParticipant
And the winner is…..
I really didn’t want to be right.
2.2.4. didn’t fix the z-index issue. Tested on virtual iPhone7 plus with Mobile Safari 10 and virtual Mac OSX 10.13 with Safari 11.Don’t think there’s anything stuck in the online simulators cache. Looks like they build the testing environment from scratch on every new test run. I’ll probably get my hands on a Mac later today so I can do some proper fiddling there.
April 11, 2018 at 17:59 in reply to: I’ve reported a bug to Themepunch/Essential Grid and they won’t look at the bug unless I have the newest version of Essential Grid #194425peterhsParticipantHoly shit – now you’re even faster than my WordPress moaning 🙂
Let’s see what happens when I run the update. I’ve got a bet running with myself and Themepunch’s support: 10% chance the update will fix the z-index problem 🙂
Time for a drum role to build the suspense.
April 11, 2018 at 17:56 in reply to: I’ve reported a bug to Themepunch/Essential Grid and they won’t look at the bug unless I have the newest version of Essential Grid #194424peterhsParticipantHi Kieran,
once again I am knocked off my socks by your super quick response time 🙂
Nice contrast to Themepunch’s kafkaesque approach to support.
Also really like that you apparently take the time to run tests before you are releasing a plugin update for Kleo. It makes sooo much sense. For all the good things WordPress has going for it – stability without surprises when updating anything or installing something new is definitely not one of them. That part actually makes WordPress core structure look more like a toy that pretends to be a tool.
And yet I keep coming back for more…
Thanks for your feedback 🙂
Cheers,
PeterpeterhsParticipantHi Kieran,
got completely sidetracked and forgot to post the results:
I finally got a hold of Themepunches support – which is a mess. At least for plugins that came in a bundle with a theme.
Anyways – they said it was known bug and it would be fixed in the next update (in February I think)
I’ve installed the latest update of Essential Grid that you made available and the problem still persists. So hurray for that.Manually fixing it would require some custom js script checking time stamps and then only making the grid visible once it has finally loaded. Which felt a little excessive and just a little out of my comfort zone in js at the moment. Luckily Essential Grid has a function that seems to do the trick.
So as a current workaround for the issue:
Go to Ess.Grid>Ess.Grid>YourGrid>Spinner. There you can choose to enable “Hide Markups before Load”. This changes the rendering behaviour in the browser enough to avoid the mouseover problem on page load. Seems to work with or without a selected spinner. Only trouble is that the div that contains the grid doesn’t have a set height that will fit the grid. So the container starts at pretty much 0 height and then slides to the needed height – which looks pretty bad on a startpage. But grabbing the containing div and giving it a min-height possibly for every breakpoint fixes that too.Not too happy about the outcome but as long as it works…. fingers crossed that a future update won’t break the workaround.
Cheers,
PeterpeterhsParticipantJust double checked: both the main site where the problem occured and the test site I was using are running php 7.0
But I had no problem on the test site with entering a new Essential Grid into the WPBakery editor. But still shitloads of options to test to narrow down the error. E.g. I don’t think my test site is running the newest version of Kleo which the main site is. Also main site is multisite whereas test site is a single site install. And the editor was working fine in the past on mainsite too.At the moment it’s only a minor problem so low priority and not quite in the mood for debugging. I’ll keep an eye on it and if I find more clues I’ll come back to you on that one.
I’ll definitely keep you posted on ThemePunch feedback for the Essential Grid issue.
Cheers,
PeterpeterhsParticipantOh, I have another issue – it might be Essential Grid related but it rather looks like it is an issue between WPBakery Page Builder and WordPress 4.9.x
The problem first popped up for me when I was trying to make changes to a Essential Grid in a Page Builder page: I couldn’t change the grid through the wysiwyg backend editor. It looks like this is affecting a lot more than just Essential Grid integration. Feels like parts of the js are not being executed properly anymore.
Haven’t spent much effort tracing the issue yet but google suggests there might be a general issue for WordPress 4.9.2 + WPBakery Page Builder + certain themesJust thought I’d ask. Maybe worth another thread in the forum?
Cheers,
PeterpeterhsParticipantHi Kieran,
wow – Sunday. And feedback in 5 Minutes? Thanks 🙂
I’ve left a comment at Codecanyon. So fingers crossed ThemePunch reads them.
Cheers,
PeterpeterhsParticipantHi Kieran,
thanks for the quick feedback.
I have tested the issue in a test install to rule out a couple of options.
The problem is not related to:
– WordPress 4.9.2
– Kleo/K Elements – (tested Essential Grid with TwentySixteen)
– Multisite
– a specific skin in Essential Grid
– lazy load options in Essential Grid
– any other plugins
– source type for Essential Grid (haven’t tested stream as an option – but I doubt it will change anything)Final test: all plugins and themes up to date. Only plugin enabled: Essential Grid.
Firefox: any grid item where the mouse pointer is hovering over it while the page is loading will break the overlay effect for that grid item.
You can test here: http://www.zinzino.rocksThis is a pure Essential Grid bug.
Cheers,
PeterpeterhsParticipantHi Laura,
I managed to fix it. It looks like I might not have had anything to do with RevSlider at all. And that it only looked like it. The problem was server side. And for the life of it I don’t know how the server does it. In any case, something can apparently tigger my server to prevent WordPress to drop the wordpress_test_cookie. And that’s missing you get the “blocked” error and no clues why.
It create the weirdest goose chase ever.
Even ran a full files system compare on the working state of the install vs. not working. Same for the DB. And there were no relevant changes. But things started getting really bizarre, when even uploading the backup files and db from the working state of the install didn’t solve the problem.
3 days wasted. And all it was, was a missing cookie.Fix:
insert this at the top of htaccess. Forces the cookie. Login works. Only possible side effect: after you have logged in for some reason then you have two test cookies in your browser.COPY CODERewriteEngine On RewriteCond %{REQUEST_URI} ^/ RewriteRule .* - [CO=wordpress_test_cookie:WP+Cookie+check:%{HTTP_HOST}:1440:/]
peterhsParticipantHi Laura,
got sidetracked a little on this.I have been able to narrow down the problem. Started with a fresh multisite install and then tested login after each new plugin. Third plugin was the charm: Revolution Slider breaks my login via Kleo Popup Login. And it’s irreversible. Tried uninstalling Revolution Slider and deleting it. No luck.
Then tried deleting Kleo from server and reinstalling it. Still not working.I’ll send you the login credientials in private message.
Cheers,
PeterpeterhsParticipantHi again.
The problem also exist for using the login widget in the sidebar.
And if I log in through /admin the problem seems to go away and I then can login using both the modal and the widget. Seems to last for some time. Hours. And then the problem comes back.
It might be related to Chrome. I haven’t seen the problem on Firefox. But that doesn’t say much since I am using Firefox to edit the site and alway log in through /admin first thing I do.peterhsParticipantSo – the problem with ‘Tabs Responsive’ got solved by this code in Kleo Child functions.php:
add_action(‘wp_print_styles’, ‘mytheme_dequeue_js_from_plugins’, 100);
function mytheme_dequeue_js_from_plugins() {
wp_dequeue_script( “wpsm_tabs_bootstrap-js” );
wp_dequeue_script( “wpsm_tabs_r_bootstrap-js-front” );
}The problem with the drop down menus is between Kleo, Events Manager and Geodirectory. And it seems to be related to both Events Manager and GeoDirectory using Google Maps API. If I set up GeoDirectory to run on OpenStreet API the drop down menus work. Also found this thread: https://geomywp.com/forums/topic/dropdown-menu-problem/
Feels like this is a similar problem.Cheers,
PeterpeterhsParticipantHi Radu,
thanks for the update. I’ll try that.Little unclear though which plugin you are referring to.
There are two problems. One as a result of “Tabs Responsive” which I assume you are referring to.
And the other is the problem that seems to originate between “Geodirectory” and “Events Manager” together. Either one of them separately doesn’t seem to cause any conflict.Cheers,
PeterpeterhsParticipantHi Radu,
got sidetracked with some other stuff.
I tried activating debug. Unfortunately the logfile doesn’t have any relevant information regarding the problems.
Disabling plugins: Like I said initially. I have identified the culprits already.
1. Events Manager stops the dropdown content for second level menu points from working. As far as I can tell, this will only occur though, when a page belonging to the plugin is displayed.
2. Tabs Responsive causes a problem for the collapsed menu for tablet/phone viewports. When you open the menu it displays for second or so and then snaps back to collapsed state.
Unfortunately neither on of them has any options for disabling any bootstrap files from overriding kleo’s bootstap files.
Do you have any suggestions how to proceed?
Cheers,
PeterpeterhsParticipantHi Radu,
your customer reviews certainly are right. Your support is awesome. Thanks for that.
Slight pickle with the current fix: The tax grids usually don’t show the meta tags. Same for the ‘continue reading’ button. Meta tags are the minor issue. Clicking the button produces and error though. I guess both could be fixed with css display:none one way or another. Not sure if my css is good enough to only disable those two on the Mooberry tax grids without affecting the rest of wordpress.
Just realized that I installed WordPress in German. Does that work for you or should I install in English or find a plugin that will change the backend to English?
Cheers,
PeterpeterhsParticipantHuh, don’t know where the http:// came from for the ftp address. In any case it’s without it.
peterhsParticipantHi Laura,
I had to reinstall Buddypress for some bizarre reason. At first it didn’t show the Base group but after reinstalling it worked a charme.
Thanks 🙂
peterhsParticipantHi Radu,
just double checked with Twenty Fifteen, Sixteen and Seventeen. They all work.I have been in touch with Christie at Mooberry and we were wondering how to get here access to Kleo so she could have a look. I could set up a wordpress site for her with admin access but maybe it would be easier if you get in contact with her directly: http://www.mooberrydreams.com/contact/
Cheers,
Peter -
AuthorPosts