Title: ppjev's Replies | WordPress.org --- # ppjev [ ](https://wordpress.org/support/users/ppjev/) * [Profile](https://wordpress.org/support/users/ppjev/) * [Topics Started](https://wordpress.org/support/users/ppjev/topics/) * [Replies Created](https://wordpress.org/support/users/ppjev/replies/) * [Reviews Written](https://wordpress.org/support/users/ppjev/reviews/) * [Topics Replied To](https://wordpress.org/support/users/ppjev/replied-to/) * [Engagements](https://wordpress.org/support/users/ppjev/engagements/) * [Favorites](https://wordpress.org/support/users/ppjev/favorites/) Search replies: ## Forum Replies Created Viewing 8 replies - 1 through 8 (of 8 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[OoohBoi Steroids for Elementor] HTML tag on container is broken by OoohBoi](https://wordpress.org/support/topic/html-tag-on-container-is-broken-by-ooohboi/) * Thread Starter [ppjev](https://wordpress.org/support/users/ppjev/) * (@ppjev) * [3 years, 12 months ago](https://wordpress.org/support/topic/html-tag-on-container-is-broken-by-ooohboi/#post-15755982) * - This reply was modified 3 years, 12 months ago by [ppjev](https://wordpress.org/support/users/ppjev/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[OoohBoi Steroids for Elementor] HTML tag on container is broken by OoohBoi](https://wordpress.org/support/topic/html-tag-on-container-is-broken-by-ooohboi/) * Thread Starter [ppjev](https://wordpress.org/support/users/ppjev/) * (@ppjev) * [3 years, 12 months ago](https://wordpress.org/support/topic/html-tag-on-container-is-broken-by-ooohboi/#post-15755914) * The problem happens, when link is enabled. Link will work, but cursor will not display as “hand”. * Also, after updating to version 1.9.7 from 1.9.6 container extras options like width disappear. You have to enter them by hand again. After reverting to version 1.9.6, all values are back. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[OoohBoi Steroids for Elementor] HTML tag on container is broken by OoohBoi](https://wordpress.org/support/topic/html-tag-on-container-is-broken-by-ooohboi/) * Thread Starter [ppjev](https://wordpress.org/support/users/ppjev/) * (@ppjev) * [3 years, 12 months ago](https://wordpress.org/support/topic/html-tag-on-container-is-broken-by-ooohboi/#post-15755491) * I see that latest version introduced some fixes to Container Extras part of the plugin, but it did not fix link hover issue that I am having. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[OoohBoi Steroids for Elementor] HTML tag on container is broken by OoohBoi](https://wordpress.org/support/topic/html-tag-on-container-is-broken-by-ooohboi/) * Thread Starter [ppjev](https://wordpress.org/support/users/ppjev/) * (@ppjev) * [4 years ago](https://wordpress.org/support/topic/html-tag-on-container-is-broken-by-ooohboi/#post-15722905) * If I disable Container Extras in the plugin settings, all starts to work fine. But it appears I am suing some of that “Container Extras” functionality. So it would be nice if problem/conflict would be sorted out. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Access Manager – Access Governance for WordPress] Redirect to Referrer page After Login](https://wordpress.org/support/topic/redirect-to-referrer-page-after-login/) * [ppjev](https://wordpress.org/support/users/ppjev/) * (@ppjev) * [4 years, 6 months ago](https://wordpress.org/support/topic/redirect-to-referrer-page-after-login/#post-15145214) * I am using default widget from AAM, redirect does not happen. I get the error: Uncaught SyntaxError: Unexpected token < in JSON at position 0 at JSON.parse( ) at XMLHttpRequest. ((index):243) * which means that response can not be parsed. If I refresh the page, I will be logged in. If I dont refresh, nothing will happen. Even errors dont appear. Any news? * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[OoohBoi Steroids for Elementor] Version 1.4.3 Killing Elementor Animations](https://wordpress.org/support/topic/version-1-4-3-killing-elementor-animations/) * [ppjev](https://wordpress.org/support/users/ppjev/) * (@ppjev) * [5 years, 11 months ago](https://wordpress.org/support/topic/version-1-4-3-killing-elementor-animations/#post-13160239) * All works fine after reenabling jQuery Migrate, thank you! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[OoohBoi Steroids for Elementor] Version 1.4.3 Killing Elementor Animations](https://wordpress.org/support/topic/version-1-4-3-killing-elementor-animations/) * [ppjev](https://wordpress.org/support/users/ppjev/) * (@ppjev) * [5 years, 11 months ago](https://wordpress.org/support/topic/version-1-4-3-killing-elementor-animations/#post-13156378) * I removed it for “performance” purposes :). I will put it back and see if it helps. Thanks! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[OoohBoi Steroids for Elementor] Version 1.4.3 Killing Elementor Animations](https://wordpress.org/support/topic/version-1-4-3-killing-elementor-animations/) * [ppjev](https://wordpress.org/support/users/ppjev/) * (@ppjev) * [5 years, 11 months ago](https://wordpress.org/support/topic/version-1-4-3-killing-elementor-animations/#post-13155744) * I can confirm, latest version kills Elementor animations. The error is as follows. Reverted to version 1.3.5, all works fine. * Uncaught TypeError: Cannot set property ‘chrome’ of undefined at child.onInit( ooohboi-steroids-min.js?ver=1.4.3:1) at child.e.each.r. [as onInit]( frontend-modules.min.js?ver=2.9.14:2) at child.Module.trigger (frontend-modules. min.js?ver=2.9.14:2) at child.e.each.r. [as trigger] (frontend-modules. min.js?ver=2.9.14:2) at init (frontend-modules.min.js?ver=2.9.14:2) at child. Module (frontend-modules.min.js?ver=2.9.14:2) at child (frontend-modules.min. js?ver=2.9.14:2) at child [as constructor] (frontend-modules.min.js?ver=2.9.14: 2) at new child (frontend-modules.min.js?ver=2.9.14:2) at e.exports.addHandler( frontend.min.js?ver=2.9.14:2) Viewing 8 replies - 1 through 8 (of 8 total)