Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #6840

    webdevep
    Participant
    Points: 11

    I’m having issues getting it work on woocom pages

    #6841

    webdevep
    Participant
    Points: 11
    This reply has been marked as private.
    #6842

    Sushi
    Staff
    Points: 199

    You can make the URL groups with the URL: http://x.com/product/ and it should work then 🙂

    Please update us how it goes.

    #6843

    webdevep
    Participant
    Points: 11
    This reply has been marked as private.
    #6844

    webdevep
    Participant
    Points: 11

    I set it to https://x.com/product/ and it didn’t work**

    • This reply was modified 8 months, 3 weeks ago by  Sushi.
    #6845

    Sushi
    Staff
    Points: 199

    Would you please send me a temporary admin access so that I can try?

    • This reply was modified 8 months, 3 weeks ago by  Sushi.
    #6846

    Sushi
    Staff
    Points: 199

    Btw, I have just tested with the URL structure you mentioned and it worked for me:
    http://take.ms/mlMRc
    http://take.ms/4lMtS

    #6849

    webdevep
    Participant
    Points: 11
    This reply has been marked as private.
    #6851

    Sushi
    Staff
    Points: 199

    Hello there

    Please check now. For some reason your server is returning https://domain.com:443 as your site url (including port no), so when the plugin compares with current url, it gets false and the menu is not replaced. I have added some code tweaks in your plugin code, and now it’s working.

    Please check and let me know.

    — Sushi

    • This reply was modified 8 months, 3 weeks ago by  Sushi.
    #6853

    webdevep
    Participant
    Points: 11

    Thank you for your help in this matter. It’s much appreciated.
    On the port thing… We use a complex server set up with serverpilot.io. It run’s apache with nginx reverse proxy with advanced caching. Which is likely nginx was returning the port number.

    Will this be fixed in future updates? If not your changes will be removed when the plugin is updated.
    Thank you again.

    • This reply was modified 8 months, 3 weeks ago by  Sushi.
    #6856

    Sushi
    Staff
    Points: 199

    Glad to hear that the issue is fixed. Yes, we have already pushed an update last week but not approved yet. After that, next week we will push another update and then this fix will be added. So, before updating ask me if the fix is included or not.

    Also, would you please leave a review in CodeCanyon if it doesn’t kill your time :)?

    Thanks again
    Sushi

Viewing 11 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic.