Posts by JayW

    Hi Hussein, thanks for your thoughts.

    I tried using your Pipit plugin to detect if user is logged in, and it works except for a small glitch. Sometimes it kicks the user out of control panel, (logs them out) when editing the page where the logged-in check is happening. This might be a glitch specific to the environment here, I'm not sure. Not a big deal, but I ended up removing the Pipit plugin and instead rely solely on a hidden URL. This was for a site help page for editors, intended to be seen only by them.

    Roles are great, but I would still like tags on top of that. So that for example "Editor Pete" could have slightly different page edit access than "Editor Penny". This would also be beneficial when giving control panel access to third parties, such as marketing agencies or copywriters who may only need access to specific pages.

    Jotted down a few notes after a recent Runway build. Most of these ideas are (probably) minor things, and some of them would not be new suggestions.

    In no particular order:

    * Last edited by, and date

    Surprising omission, but it would be great if all editable items in the control panel showed "Last edited by (user) on (date+time)." Bonus points for clicking that text to get a full history of edits for that item.

    * Dangerous Undo

    Possibly the world's most dangerous undo button. This loaded shotgun reverts to previous version and publishes immediately without a re-do safety net. Unless editors expect that behaviour, they may get a surprise. Suggestion might be a confirmation prompt stating what is about to happen, or even a label change to something like "revert"; or just add a re-do safety net.

    * Control panel side navigation

    Another world first - a menu with pagination - its own back button! Nobody gets it. I ended up making a custom menu for editors, which is great, but there's still an awkward back arrow and "pages" item above the custom menu. I'd like to hide that, leaving only the custom menu.

    * html links in notes-before

    Love the notes-before feature. Would love even more if I could pop an HTML link in there, so I could open a new tab with some more information for editors.

    * Tags for perch editors, similar to member tags.

    Or just a solution to have certain pages hidden or inaccessible in the control panel, from certain editors. Currently it's all or nothing.

    * If (user X is perch editor with tag y) then show page.

    Following on from above suggestion, a way to display pages on the site only if editors are logged in to control panel, and have specific tags, otherwise the page returns a 404. So basically just like member tags, except for perch control panel users. It's not practical to have editors "sign up" again to the site, just so they can see exclusive site content meant for staff only.

    * The help link in top right should open new window/tab

    Navigating away from the edit form can cause problems when going back. The help link should open new tab by default.

    * Option to omit assets from search results.

    Using global search in control panel returns everything including resources. The problem is these resources can pollute the returned results. If the user is trying to find a collection item, it would be helpful if they could optionally exclude resources from the returned results.

    My 2 cents: I support perpetual license with maintenance as a good compromise.

    Out of box thinking - I wonder what would happen if Perch was offered for free, and Runway increased by the price that Perch was? Or have a free edition where everything worked, but put hard limits on collection item/product counts? Marketing and incentives for new users are important, and these things could be improved for Perch.

    As a creative frontend dev I've been working with CMS systems since Vignette Story Server days of late 90's early 00's. It no longer exists, the founders retired early having made millions from hard-selling their clunky difficult system to enterprise. But is that the goal? To make millions and retire early? Story Server was bad, but I've seen a lot worse in the CMS space. Perch Runway is a breath of fresh air compared with memories of clunky control panels of the past, or "do you want fries with that" plugin ecosystems of the present. Wordpress gives me a headache, there's always something bleeting at you for attention in the admin panel. Perch is more relaxed, and I hope that continues. It needs to continue one way or the other!

    Our new site soft-launched recently. We are happy, it's performing well.

    Highlights are the "new equipment" section with product selector, filtering the collection items.

    Almost everything is editable via CMS, so the site can last a long time as it's highly configurable by editors.

    I really like the Perch template engine and all the useful attributes and possible functions. Our company has several websites for different businesses, many of them clunky old Wordpress. When I came on board I suggested moving away from Wordpress to something better, leaner, faster, friendlier. We will probably be getting more licenses later on. The Perch docs, this forum and the old forum have been very helpful with advice on how to do certain advanced things, or clarify concepts.

    Looks like you're trying to execute jquery before the document is ready.

    This bit here:

    1. $("#footer_quick_contact_form").validate({...

    You need to put any jquery in the document ready function....

    1. $(document).ready(function(){
    2.     $("#footer_quick_contact_form").validate({...
    3. });

    Required reading:

    I'm guessing this might be the problem, but there's a lot of bloat on the page and the problem might be something else.