Jump to content
DevFuse Forums
  • Urls not working after garage import


    Michael
    • Fixed IP.Board Version: IP.Board 4.2.x

    "Garage" urls don't work after importing the garage app into the collections app.

    Manual Patch:

    Open ACP > System tab > Advanced Configuration > Friendly Urls tab. Revert all the "garage" entries and re-add the "garage" text again.



    User Feedback

    Recommended Comments

    That has done the trick for me EXCEPT I've got a few stubborn ones, namely this one changes itself to:

    collections/garage/item/{#id}-{?}

    The other one or two that had also done that - I found them on Garage FURL settings page and deleted them but that one doesn't want to budge. Really weird.

    Share this comment


    Link to comment
    Share on other sites
    23 hours ago, cybernck said:

    After reverted them all to the Collections FURLs and trying to set them (or it, rather).

    As last check this was actually an IPB4 bug itself. i.e. It was affecting IPS's own apps as well.

    Have you got any other furl customizations in place and what IPS apps have you got installed? I might try and reproduce this locally and see what I can do on my end.

    Share this comment


    Link to comment
    Share on other sites

    I've done some investigating myself. IPS Support has just told me the following:

    Quote

    Unfortunately, the first item in the FURL cannot be altered as such in this case. This is also the case with other FURLs, even our base FURLs, like "calendar" cannot be removed for "events" or similar.

    What I don't understand though is how was I able to change all the other Collections FURLs then. Might have been lucky, haha.
     

    Someone has just posted some info on how to fix this bug here:

    https://invisioncommunity.com/forums/topic/433280-error-with-furl-changes/?page=2&tab=comments#comment-2714900

    Edited by cybernck

    Share this comment


    Link to comment
    Share on other sites

    I believe this was allowed before, it's only recently in the last few versions have I had reports of this. So not sure why they've changed it. I assume that patch you linked to works for you? If so, I might just include a link or reference it somewhere in the docs.

    Share this comment


    Link to comment
    Share on other sites
    56 minutes ago, cybernck said:

    I haven't tried it yet, wanted to hear your opinion first.

    If the IPB4 code has been changed to prevent changes through the acp itself. Then either the code will need to be modified to remove that or changed through the furl.json file. The later is just as good as long as you be careful to maintain the structure of the file. i..e not remove a closing bracket or bit of code apart from the friendly words itself.

    Share this comment


    Link to comment
    Share on other sites

    OK, I've changed "topLevel": "Collections", to "topLevel":  "",  and it has worked! But not before I've clicked on "revert" to have it reset to no prefix first. I've tried with some other FURLs too, just to make sure it works fine - and it does.

    It still doesn't explain why I initially managed to change all the other ones, except that one (first in the list). There were a couple that were stubborn, giving me some strange errors. For some reason, they showed up in the App > Collections > FURL settings page where I clicked on revert and then managed to change them.

    Share this comment


    Link to comment
    Share on other sites


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

    Pending = We are still working on this report.

    Fixed = The issue has been fixed and the resolution will be available in the next version.

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

×
×
  • Create New...