Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter florentd53

    (@florentd53)

    Hello. Thank you for this information.
    However, it is not exactly my question and not what I want.
    I do not want users other than subscriber to be able to book events. Allowing them to do so, just to allow them to see the events is risky. Even if on their subscription calendar the booking button is absent (because they can also end up on the subscribers booking page. I may manage to prevent them to by other means but it is risky).
    My question was more “Why can editors (and also administrators) see the events even though they are not allowed to book it?” (which is what I want also for authors and contributor so I wanted to find out what conditions made it possible) and you are telling me this is theroretically impossible… (but in fact it is for editors!)

    I just like was done in the temporary version, I changed the following “$” by “jQuery” in the “shortcode.js” file (in assets/js):
    Line 703
    Line 706
    Line 718
    Line 721
    Line 722
    And it works.
    I imagine this could be confirmed in the main version for a subsequent update?
    Best regards
    Florent

    Indeed the version in https://drive.google.com/file/d/1eFWGo_ZNdW07j5Hh8gQERlioht0HE_CN/view?usp=sharing does fix the problem.
    I am currently looking at what exactly fixed it so that it can be added to the main version.
    Florent

    Hello Dylan
    I am also discovering your plugin and hope to make good use of it on 2 websites I am or will be managing (including possibly the pro version on one of them)
    However, I am using version 3.2.2 of the plugin and it seems I have the same issue as mentionned by Frankie : the [zephyr_new_task_button] successfully displays the button but when clicked nothing happens. Opening the dev console reveals the same error (Uncaught TypeError: $ is not a function) (shortcodes.js?ver=5.6.2:703, shortcodes.js?ver=5.6.2:711 and shortcodes.js?ver=5.6.2:61)
    It seems odd because I imagine the correction has of 6 months ago was likely to have been included in the lattest version of the plugin no?
    I will try the version linked above.
    Note: I have tried on 2 websites, and using 3 different browsers : Edge, Firefox and Brave (initialy I thought it was due to a problem specific to Brave but no)
    I thank you in advance
    Best regards
    Florent

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