Rename an APP in the Perch menu - "Blog" to "Projects"

  • In the past, we have had success with editing the lang txt file (en-gb.txt) to rename menu options and buttons inside an app, such as Blog. This still works, but for some reason, we can't rename the actual nav link "Blog".


    Code
    1. "Blog": "Projects",


    Does this no longer load from the txt file in the app folder? We looked into the core file but can't see any Blog reference. Any help appreciated.


    Suggest this as a future add on, to be able to rename app link name in CMS - to make it easier for clients.

  • drewm

    Approved the thread.
  • Point taken on feature suggestion... however Runway is a different product.
    Are you suggesting I upgrade client to Runway just to rename "Blog" to "Projects" in the CMS menu?


    If you can point us in the right direction to edit in DB or **** files etc, we can get by for now.


    Thanks.

  • Hi Stuart


    You are correct: Perch Runway is a different product.


    Perch Blog is also a different product. The app is what determines what it should be called in the menu, which is a fair behaviour.



    Also the Blog app is specifically designed for date-ordered content as specified in the documentation:


    Use of the Blog App for non-date ordered content

    We sometimes see people trying to use the Blog App for things that are not a blog or news listing. This is not usually what you want to do. All of the filtering, sorting and category functionality is available in regular Perch Content. Try using that before attempting to turn Blog into something it isn’t!


    So perhaps you're misusing the Blog app by using it to manage Projects? Regular Perch gives you the flexibility to create fully-customisable multiple-item regions and you have complete control over what the region called. As for the menu link in this case, the Perch API also allows you to create apps: you can create an app to just list a link to a multiple-item region in the main sidebar menu if you can't upgrade to Runway.



    The way I see it:

    • Perch: designed and often used for smaller sites, doe not have a Menu Manager (reasonable)
    • Perch Runway: designed and often used for larger sites, has a Menu Manager (reasonable)
    • Perch Blog: a free add-on. It does not have a feature to let you customise its name in the menu (reasonable)





    If it is too late into the project to start using a multiple-item region instead of the Blog app and you cannot upgrade to Runway, you can write some JS to change the link title as Perch allows you to add your own CSS and JS to the control panel. This way at least you won't breach your license agreement (and hence lose support) by modifying core files.

  • Thanks for your tips. Yes, I should not have mentioned editing the **** files... never have before.

    Thing is, you used to be able to edit the lang txt file to change this and you can still change all the other headings and buttons within the app. Not a big deal really. Certainly not worth changing to Runway or spending more time on.


    As for comparing the Blog App to repeating content lists/regions etc, not really the same out of the box.

    For some things yes, they are useful. We have tried both and built over 25 sites, with Runway too.