Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Has this been updated yet? shortcode [booking_package id=x services=y] does not work. Can you update me on how could this work thanks and more power.

    Thread Starter bennylumad

    (@bennylumad)

    Hi deepen,

    Yes i noticed that it takes a heavy toll when you put all the shortcodes in one place. But, since we are using live meeting shortcodes that’s an option of convenience on our side so we can update automatically the recurring time and descriptions on the live meetings without going to any of the individual pages.

    Anyway, thank you very much for your reply and more success to your plugin. We really appreciate the help you put out in these times were everybody is staying home doing work.
    Cheers!

    Thread Starter bennylumad

    (@bennylumad)

    @fdittmar

    Hey, if you don’t mind – How did you limit the plugin to a single page / set of pages?
    – Please refer to these steps – https://kinsta.com/blog/disable-wordpress-plugins-loading/

    And do you delete expired meetings from that page manually? (to keep the display clean)
    – yes, we update them accordingly.

    Thread Starter bennylumad

    (@bennylumad)

    Hi Deepen,

    We create zoome meetings via zoom dashboard directly, and we just embed the shortcodes from via live meetings from each user (pro account) that has created a meeting of to a single page. We call this ‘Current Live Meetings‘ Page and that is where all the shortcodes go, this is via live meetings and all of them are reccurring. There is a very noticeable increase on page load on all of the pages Frontend/backend as i’ve said above, it happens all over site.

    I found a work around for this via only enabling the/your plugin unto a specific page since all of the shortcodes are just in one page. All the the other pages without the zoom shortcode is back to normal 2-3sec load speed, while the page that has the shortcode embeded is loading around 5-10sec more, since it’s only requesting api calls to that page only – we have mitigated that issue for now. If you can work this around on future updates of the plugin that would be great. Thank you and more success to you 🙂

    Thread Starter bennylumad

    (@bennylumad)

    Thank you for your awesome work.

Viewing 5 replies - 1 through 5 (of 5 total)