Forum Replies Created

Viewing 15 replies - 1 through 15 (of 20 total)
  • I had a day of lost sales, fortunately just a day because I have been actively monitoring the site. I only noticed it because I went through checkout as a guest and saw no payment options. Because my Square, Stripe, and PayPal had all be disconnected with the most recent plugin update.

    Thread Starter hagentertainment

    (@hagentertainment)

    ok thank you because otherwise I really like your pluginnand the variety of payment options. I would like to keep using it.

    Could you try create a new rule set and plugging that into the pluging settings? With the new ruleset, just wipe out all of the IP addresses. Those IPs will still be blocked with the old ruleset that will still be active but the plugin will add any new IP addresses to the new ruleset. That’s just what I’m thinking for now until a more permanent solution can be found.

    Hi. I noticed you didn’t get a response. Did you ever figure it out? I was able to get it up and running in less than 5 minutes. There is a really good video towards the end of their website: https://polarmass.com/polar-mass-advanced-ip-blocker/

    Thread Starter hagentertainment

    (@hagentertainment)

    Thank you. For now, I have rolled back to version 3.X until my theme updates the code.

    Thread Starter hagentertainment

    (@hagentertainment)

    Disregard the last screenshot with the database because I must not have deleted all of the records. Those are locations for different events. I did finally clear out all locations for all events and then went back in and tried to add a location for just one event. The l”a:4:{s:7:”address”;s:59:”Localhost Philly, North Broad Street, Philadelphia, PA, USA”;s:8:”place_id”;s:27:”ChIJDY4-SmXIxokR9yHqSx04ALQ”;s:8:”latitude”;d:39.959724399999998922794475220143795013427734375;s:9:”longitude”;d:-75.1615599999999943747752695344388484954833984375;}” but for some reason the value is still being handled as an array.

    Thread Starter hagentertainment

    (@hagentertainment)

    I updated the core plugin to 4.0.8 and I still encountered a fatal error. This time the error read:

    PHP Fatal error: Uncaught TypeError: Illegal offset type in /home/hagent6/public_html/dev/wp-content/themes/evenex/core/helpers/functions/global.php:585 Stack trace: #0 /home/hagent6/public_html/dev/wp-content/themes/evenex/components/editor/elementor/widgets/eventin/eventin-events.php(55): get_evenex_event_location() #1 /home/hagent6/public_html/dev/wp-content/themes/evenex/components/editor/elementor/widgets/eventin/eventin-events.php(93): Elementor\Multi_Event_Widget->get_event_location() #2 /home/hagent6/public_html/dev/wp-content/plugins/elementor/includes/base/controls-stack.php(2386): Elementor\Multi_Event_Widget->register_controls() #3 /home/hagent6/public_html/dev/wp-content/plugins/elementor/includes/base/widget-base.php(1065): Elementor\Controls_Stack->init_controls() #4 /home/hagent6/public_html/dev/wp-content/plugins/elementor/includes/base/controls-stack.php(569): Elementor\Widget_Base->init_controls() #5 /home/hagent6/public_html/dev/wp-content/plugins/elementor/includes/base/widget-base.php(192): Elementor\Controls_Stack->get_stack() #6 /home/hagent6/public_html/dev/wp-content/plugins/elementor/includes/base/controls-stack.php(314): Elementor\Widget_Base->get_stack() #7 /home/hagent6/public_html/dev/wp-content/plugins/elementor/core/files/css/global-css.php(120): Elementor\Controls_Stack->get_controls() #8 /home/hagent6/public_html/dev/wp-content/plugins/elementor/core/files/css/global-css.php(66): Elementor\Core\Files\CSS\Global_CSS->render_schemes_and_globals_css() #9 /home/hagent6/public_html/dev/wp-content/plugins/elementor/core/files/css/base.php(680): Elementor\Core\Files\CSS\Global_CSS->render_css() #10 /home/hagent6/public_html/dev/wp-content/plugins/elementor/core/files/base.php(180): Elementor\Core\Files\CSS\Base->parse_content() #11 /home/hagent6/public_html/dev/wp-content/plugins/elementor/core/files/css/base.php(131): Elementor\Core\Files\Base->update_file() #12 /home/hagent6/public_html/dev/wp-content/plugins/elementor/core/files/css/base.php(227): Elementor\Core\Files\CSS\Base->update() #13 /home/hagent6/public_html/dev/wp-content/plugins/elementor/includes/frontend.php(1027): Elementor\Core\Files\CSS\Base->enqueue() #14 /home/hagent6/public_html/dev/wp-content/plugins/elementor/includes/frontend.php(649): Elementor\Frontend->parse_global_css_code() #15 /home/hagent6/public_html/dev/wp-includes/class-wp-hook.php(324): Elementor\Frontend->enqueue_styles(”) #16 /home/hagent6/public_html/dev/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #17 /home/hagent6/public_html/dev/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #18 /home/hagent6/public_html/dev/wp-includes/script-loader.php(2263): do_action(‘wp_enqueue_scri…’) #19 /home/hagent6/public_html/dev/wp-includes/class-wp-hook.php(324): wp_enqueue_scripts(”) #20 /home/hagent6/public_html/dev/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array) #21 /home/hagent6/public_html/dev/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #22 /home/hagent6/public_html/dev/wp-includes/general-template.php(3065): do_action(‘wp_head’) #23 /home/hagent6/public_html/dev/wp-content/plugins/elementskit-lite/modules/header-footer/views/theme-support-header.php(11): wp_head() #24 /home/hagent6/public_html/dev/wp-content/plugins/elementskit-lite/modules/header-footer/theme-hooks/theme-support.php(25): require(‘/home/hagent6/p…’) #25 /home/hagent6/public_html/dev/wp-includes/class-wp-hook.php(326): ElementsKit_Lite\Modules\Header_Footer\Theme_Hooks\Theme_Support->get_header(NULL) #26 /home/hagent6/public_html/dev/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #27 /home/hagent6/public_html/dev/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #28 /home/hagent6/public_html/dev/wp-includes/general-template.php(38): do_action(‘get_header’, NULL, Array) #29 /home/hagent6/public_html/dev/wp-content/themes/evenex/template/homepage-template.php(6): get_header() #30 /home/hagent6/public_html/dev/wp-includes/template-loader.php(106): include(‘/home/hagent6/p…’) #31 /home/hagent6/public_html/dev/wp-blog-header.php(19): require_once(‘/home/hagent6/p…’) #32 /home/hagent6/public_html/dev/index.php(17): require(‘/home/hagent6/p…’) #33 {main} thrown in /home/hagent6/public_html/dev/wp-content/themes/evenex/core/helpers/functions/global.php on line 585

    Let me back up for a minute. I am updating the plugin because I’m not sure when but a few weeks back, the location of my events started appearing as “Array”. Please see the screenshot, the red is showing the location appearing incorrectly in the event header but appearing correctly in the event sidebar.

    The php error message has something to do with all of my locations for some reason being detected as arrays and therefore causing an “illegal offset type”. I’m not sure when this issue started happening but I noticed it a few days ago. Previous the location in the banner/header area was showing correctly and matching that of the side bar.

    I was able to resolve the critical error by going into PhpMyAdmin and executing the SQL “DELETE FROM wpstg2_postmeta WHERE wpstg2_postmeta.meta_key = ‘etn_event_location'”;

    I tried going back to the admin area and editing my events to re-input the location. I type in “Localhost Gaming Lounge, 401 N Broad St, Philadelphia, PA 19108”. When I save it, I see see the “Array” text pop up in the banner/header area. Also, my map on my event page looks like this:

    After trying to add my location again, this is what appears in my database (all of these records are for the one event which is why the output is showing as an array

    Thread Starter hagentertainment

    (@hagentertainment)

    I tried viewing /plugins/eventin-pro/core/settings/settings.php but no such file exists. Inside of the settings folder there is a folder called “views” and that’s it. Inside of views there are two files named country-info.php and email-notification-settings.php

    Hello. I have the same question and I’m very confused about your response. I have a newer multisite network where we just expanded with around 8 new subsites after having our first main site active over a few years with no other subsites. So currently, all of our user registrations have been done under the main site. We have installed and activated your plugin. Our users/customers are very likely going to be interested in our subsites but now when they register for any of those, they get the error message that their account already exists (which is does for the main/old site).

    My confusion is, given your plugin’s functionality, shouldn’t it be that those existing users are only registered for the main site and not for the new subsites? I don’t see why that would mean that existing users then couldn’t register for the new subsite.

    Is there a way to convert those existing users to be registered for just the main site? Maybe I’m confused by how your plugin works. I read statements saying that it allows a user to register for just a specific subsite and not the network overall. So I would imagine that means there is some sort of metadata or something that assigns newly registered users to the subsite under which they registered. I don’t understand how this couldn’t apply retroactively.

    Hello. Did you find a solution? I’m also having issues with logging in/out and I’m running a multisite as well.

    This is my experience as well.

    I’m also interested in achieving this

    Thread Starter hagentertainment

    (@hagentertainment)

    Thank you, that got me started in the right direction.

    Thread Starter hagentertainment

    (@hagentertainment)

    Sorry, no I’m not using that extension (or any other add-on).

    Thread Starter hagentertainment

    (@hagentertainment)

    Hello. I think I am close to finding a way around the permalink issue.

    I’ve added the following code to my theme functions file.

    add_action( 'init', 'hag_rewrites_init' );
    function hag_rewrites_init(){
        add_rewrite_rule(
            'directory\/(podcasts|communities|shops)(\/?)$',
            'index.php?page_id=396102&directory_type=$matches[1]',
            'top' );
    }

    396102 is my directory page ID. Currently when someone goes to domain.com/podcasts they are shown my entire directory, which is nice- it’s a step above them seeing the unformated archive page. The issue is the page isn’t showing the listings for JUST the listing type I have specified (in this case “podcasts”). This is because the
    &directory_type=$matches[1]
    part of the string is incorrect. I believe I am using the wrong query variable. Maybe it should be something else instead of “directory_type”. It’s also possible that instead of passing the text slug of the listing type “podcasts”, I need to pass it’s numeric ID.

    Do you have any insight on how I can resolve this? I’m almost there.

Viewing 15 replies - 1 through 15 (of 20 total)