flux

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 20 total)
  • Author
    Posts
  • in reply to: Uncaught SyntaxError: Unexpected token ) #24840

    flux
    Member

    Hi Dylan,

    So did you just add a polygon? or did you do something else aswel?
    I’m just asking, in case we have the same problem again on other sites, we can fix this ourselves.

    Kind regards,
    Shane

    in reply to: Uncaught SyntaxError: Unexpected token ) #24815

    flux
    Member
    This reply has been marked as private.
    in reply to: 403 errors due to // in url #24611

    flux
    Member

    Hi Dylan,

    Thanks again for your reply. I’m compressing it now as we speak and I’ll send you an email in a couple of minutes.

    Kind regards,
    Dirk

    in reply to: 403 errors due to // in url #24565

    flux
    Member

    Hi Dylan,

    Thank you for the time you put into this. We do use a 3rd party installer from our host ‘Siteground’ and indeed we use the same theme/framework for all our sites named: Bridge.

    Kind regards,
    Dirk

    in reply to: 403 errors due to // in url #24535

    flux
    Member

    Sorry for the spam.
    I see in the basic plugin you have this:

    <link rel="stylesheet" type="text/css" media="all" href="<?php echo wpgmaps_get_plugin_url(); ?>css/data_table.css" />

    In pro you have this:
    <link rel="stylesheet" type="text/css" media="all" href="<?php echo wpgmaps_get_plugin_url(); ?>/css/data_table.css" />

    Unless basic have problems with other users, I believe you can leave the slash in pro too. Also for JS and images. But, you may know way more them me in this. This is just a thought.

    in reply to: 403 errors due to // in url #24534

    flux
    Member

    Is there a quick way for us to fix this so we can use this fix on all our websites?

    in reply to: 403 errors due to // in url #24533

    flux
    Member

    Hi Dylan,

    Thank you for your quick reply.
    Is there anything I can help you with to replicate this?

    in reply to: 403 errors due to // in url #24511

    flux
    Member

    Dear Dylan,

    It’s been a while and unfortunately the double slash error is still not fixed. We use the pro/gold version on different sites and plan or want to be able to use it on our future sites but the double slash issue persists and makes the plugin unusable for us.

    I would like to know if there is a fix coming for this issue.

    Please let me know asap.

    Kind regards,
    Dirk

    Attachments:
    You must be logged in to view attached files.
    in reply to: 403 errors due to // in url #23660

    flux
    Member

    That would be nice, thanks.

    in reply to: 403 errors due to // in url #23638

    flux
    Member

    Hi

    Yeah sorry, I figured out how to fix this problem myself. But after every update I have to delete the extra ‘/’. And for some reason I can’t update to the latest gold version, normally the update gets pushed so I can update, but this doesn’t happen.

    Is there a solution for fixing the bugs with the extra ‘/’. Because it’s a pain in the ass to do this every time I update the plugin.

    Thanks

    in reply to: 403 errors due to // in url #23607

    flux
    Member

    [quote quote=23606]Hi

    It works again, not getting any errors anymore at the backend.
    But now I’m receiving errors in the frontend (inspect element), screenshot attached.
    I guess some files haven’t been linked properly, but I could be wrong.

    Can I ask how you solved the problems at the backend? If it is an easy fix, because we’re using the plugin on multiple sites, so we can fix this ourselves.

    Thanks

    [/quote]

    After installing the gold version I’m getting the same errors as before, but now for the gold version. Also I created a new map while it was working, but now the maps disappeared from the site.

    Sorry for the inconvenience.

    in reply to: 403 errors due to // in url #23606

    flux
    Member

    Hi

    It works again, not getting any errors anymore at the backend.
    But now I’m receiving errors in the frontend (inspect element), screenshot attached.
    I guess some files haven’t been linked properly, but I could be wrong.

    Can I ask how you solved the problems at the backend? If it is an easy fix, because we’re using the plugin on multiple sites, so we can fix this ourselves.

    Thanks

    in reply to: 403 errors due to // in url #23569

    flux
    Member

    Thanks for the fix, but after the new update a few minutes ago. I’m receiving the errors again.

    in reply to: 403 errors due to // in url #23552

    flux
    Member

    Thanks, It’s working fine.
    What was the issue, if I may ask?

    in reply to: 403 errors due to // in url #23503

    flux
    Member
    This reply has been marked as private.
Viewing 15 posts - 1 through 15 (of 20 total)