johannesdb
Forum Replies Created
-
Forum: Plugins
In reply to: [View Admin As] Issue with url parameters for adminsHey @keraweb
sure π Tested and the patch works π
Forum: Plugins
In reply to: [View Admin As] Issue with url parameters for adminsHey @keraweb
cool! Thanks for the patch!
Yup, we are aware that our urls are not quite compatible with wordpress. But they are with the js-library that we use. And there are no good ways to make wordpress compatible urls, that contains arrays. So it is a trade off.
Do you know when the next release will be out?
Forum: Plugins
In reply to: [View Admin As] Issue with url parameters for adminsHowever this is the culprit!
/** * Compat with front and WP version lower than 4.2.0. * @since 1.6.4 * @link https://developer.wordpress.org/reference/functions/wp_admin_canonical_url/ */ if ( ! is_admin() || ! VAA_API::validate_wp_version( '4.2' ) ) { // $this->add_action( 'wp_head', array( $this, 'remove_query_args' ) ); }
When I uncomment that line, the url is not changed π
Forum: Plugins
In reply to: [View Admin As] Issue with url parameters for adminsHi @keraweb,
sure! Just tried – no change :-/
Forum: Plugins
In reply to: [View Admin As] Issue with url parameters for adminsHi @keraweb,
Thanks for the fast answer!
I have tried to disable only this plugin and then the urls are not changed. I can’t say if it interacts with another plugin on the site and that is the issue. But disabling the view as plugin always solves the issue.
If you want, send me mail to get access to a site where you can see the issue.
/Johannes
- This reply was modified 1 week, 1 day ago by johannesdb.
Forum: Plugins
In reply to: [Category Ajax Filter] Fatal error when PRO is enabledHi
that seems to work better π
Forum: Plugins
In reply to: [Category Ajax Filter] Fatal error when PRO is enabledAnd on the front end I get:
Posts found: errorForum: Plugins
In reply to: [Category Ajax Filter] Fatal error when PRO is enabledI get this fatal error with those two versions enabled:
Fatal error: Uncaught Error: Class “CategoryAjaxFilterProBase” not found in /home/ugdata/outdoor365.dk/wp-content/plugins/category-ajax-filter-pro/caf-pro.php:42 Stack trace: #0 /home/ugdata/outdoor365.dk/wp-content/plugins/category-ajax-filter/admin/functions.php(394): TC_CAF_PRO->check_license() #1 /home/ugdata/outdoor365.dk/wp-includes/class-wp-hook.php(326): CAF_load_scripts->conditionally_add_scripts_and_styles() #2 /home/ugdata/outdoor365.dk/wp-includes/plugin.php(256): WP_Hook->apply_filters() #3 /home/ugdata/outdoor365.dk/wp-includes/class-wp-query.php(3530): apply_filters_ref_array() #4 /home/ugdata/outdoor365.dk/wp-includes/class-wp-query.php(3824): WP_Query->get_posts() #5 /home/ugdata/outdoor365.dk/wp-includes/post.php(6118): WP_Query->query() #6 /home/ugdata/outdoor365.dk/wp-content/plugins/divi-pixel/includes/options/settings.php(545): get_pages() #7 /home/ugdata/outdoor365.dk/wp-content/plugins/divi-pixel/includes/options/settings.php(735): DiviPixel\DIPI_Settings->get_wp_pages_list() #8 /home/ugdata/outdoor365.dk/wp-content/plugins/divi-pixel/includes/options/settings.php(578): DiviPixel\DIPI_Settings->create_general_tab_fields() #9 /home/ugdata/outdoor365.dk/wp-content/plugins/divi-pixel/includes/options/settings.php(177): DiviPixel\DIPI_Settings->create_fields() #10 /home/ugdata/outdoor365.dk/wp-content/plugins/divi-pixel/includes/options/settings.php(90): DiviPixel\DIPI_Settings->get_fields() #11 /home/ugdata/outdoor365.dk/wp-content/plugins/divi-pixel/includes/plugin.php(178): DiviPixel\DIPI_Settings::get_option() #12 /home/ugdata/outdoor365.dk/wp-content/plugins/divi-pixel/includes/plugin.php(11): DiviPixel\DIPI_Plugin->load_dependencies() #13 /home/ugdata/outdoor365.dk/wp-content/plugins/divi-pixel/includes/plugin.php(319): DiviPixel\DIPI_Plugin->__construct() #14 /home/ugdata/outdoor365.dk/wp-content/plugins/divi-pixel/divi-pixel.php(37): require_once(‘/home/ugdata/ou…’) #15 /home/ugdata/outdoor365.dk/wp-settings.php(473): include_once(‘/home/ugdata/ou…’) #16 /home/ugdata/outdoor365.dk/wp-config.php(104): require_once(‘/home/ugdata/ou…’) #17 /home/ugdata/outdoor365.dk/wp-load.php(50): require_once(‘/home/ugdata/ou…’) #18 /home/ugdata/outdoor365.dk/wp-admin/admin.php(34): require_once(‘/home/ugdata/ou…’) #19 /home/ugdata/outdoor365.dk/wp-admin/post.php(12): require_once(‘/home/ugdata/ou…’) #20 {main} thrown inΒ /home/ugdata/outdoor365.dk/wp-content/plugins/category-ajax-filter-pro/caf-pro.phpΒ on lineΒ 42
That worked π Thanks!
Cool! I will test it out at once π
I was wondering if the fix has been released? I haven’t seen any mention in the release notes.
Hi @hesseldejong,
any time frame on a solution to the issue? My clients are quite eager to take advantage of this new cool goal-feature π
Hi,
Ah, that makes sense! I hope that can be fixed π
In the ideal world I would like to know which beer’s heart and overlay has been clicked. But for now it is enough to know that a heart or an overlay on that page has been clicked.
And thanks π I will pass that on to my client π
Hi @jarnovos
sorry for taking so long to test and reply.
I added the tracking class to the elementcontainer – no clicks registered.
Made a new goal, where I track clicks on class elementcontainer – no clicks registered :-/
I assume the clicks would be registered and visible in the goal with no or very short delay?
Furthermore I would like to track clicks inside the elementcontainer and not just the elementcontainer. I want to track clicks on the heart (add to favorite) and on the image/title -> open the beer in a modal
- This reply was modified 7 months, 2 weeks ago by johannesdb.
- This reply was modified 7 months, 2 weeks ago by johannesdb.
This is an image of the config for a goal that should track a click on an element.