Perch users and Blog authors are very deliberately different things. Take the example of having a user who posts a load of blog posts over time and then leaves the company. You need to delete their user account, but then what would happen to their posts? Just because the user account is no longer needed, that doesn't mean those blog posts should have to change or be removed.
I don't understand where this 'related-to' keywords goes or what it would do. Could you post a new suggestion post with a worked example of what you're trying to achieve?
Where does this 'vars' keyword go? How is it different from PerchSystem::set_vars() ?
The second one has been done! It's in Blog now and is being rolled out to the other apps as they're updated
Good stuff! Just being able to sort by a custom date field will help a great deal with using the shop apps to sell events tickets. My temporary workaround is to insist that product codes are formatted as YYYYMMDD.
It takes three clicks to delete one image, then I'm taken back to the first asset screen. It's annoying when all the images I need to delete are on page 10.
At least a tick box next to each image on the page, so multiple images on the page can be deleted would be helpful.
I would like better control over the navigation menus. In my opinion the only thing wordpress does better is the navigation, you can add custom links, have items that display a dropdown rather than link to a page and lots of other stuff.
I don't use the Perch navigation at the moment as I just find it too restrictive.
A stripe app would also be cool but I see your already working on that.
Just thought of another very useful one: right now, perch_search_form() helps you limit search to a given directory... but what if you could limit that search to a given collection instead?
I would like to add my voice to the chorus for an update to the events app: recurring events, start and end date and time, repeating field functionality.
Also, I would like to see the members app frontend login work with the existing admin/editor backend accounts, so say staff are using Perch as an intranet they won't require two separate logins.
An option in Forms to enter a comma delimited list of words to disallow (mark as spam). Eg Viagra,pharmacy etc. as well as a list of ip addresses to disallow.
User roles for collections, routes or particular collections as they are created. We work on trust with our editors, but still may be useful to protect from a potential saboteur.
Addendum I just noticed when I logged in as a non-admin user with different rights that you already have these controls built in. I see that an editor wouldn't see a collection (sample in this case is for a people collection) unless they
Use the side bar search
The Collection is added to the App menu
The Collection is checked that it can be managed from a particular page (and that user has rights to manage that page)
Under Collection Options admin can assign which user role can manage a particular collection
All these work great!
Seems like routing is hidden from non-admin users as a default too. So features delivered!
Import tool to help migrate WordPress sites content into collections. This would help get content out of WordPress on sites that aren't blog-like but instead use WP as CMS with meta fields or custom fields.
So a developer might build their Perch template and import into those fields like Magic.
Maybe like an Import API to import content into collections or perch templates that Perch developers can adapt client data not tied to one particular CMS such as like EE, Drupal or WP. This might be in the works as I've seen the Perch logo on GatherContent. https://gathercontent.com/how-it-works-for-agencies
As an aside with hopefully helpful background info about wrangling content in WP, I use WP Migrate DB to move content between dev, staging and production WP sites to fix urls and remove serialized content https://wordpress.org/plugins/wp-migrate-db/ and WP All Import Pro for CVS and XML import into WP https://www.wpallimport.com. Maybe some of the work could be offloaded into tools like these so core function would be to get it into Perch and developers figure out how to wrangle their data to get it ready for import. You know, more magic!
I think it would be useful to have an overview of all page titles/meta descriptions within a specific site. For example, a list view of all page titles and descriptions (possibly displayed on a single page but might have to be paginated on larger sites).
Currently, this is done on a page-by-page basis in the Page Details section but I think a "page details view" as above would give users a much better overview of these attributes for the whole site. The view could be customisable to include other page <head> section items if required.
This "By Page Details" list view could be a link on the right of By Region Type in the filter bar. Each "Page Details" item could have an Edit button adjacent to it.
Wanted to refer back to a past post in the forum about adding a <perch:notes> </perch:notes> tag block to let Perchers add info about a template for developers that wouldn't be rendered during runtime.
When logged in as Admin you can go into the settings under pages and check the box "hide regions you can't edit". So when the editor is logged in they might see a page called "widgets" for example but when they click on it there are zero regions. This works as expected but what if there was an option to hide the page all together if there were zero region for that editor? This would make the admin experience even more cleaner for a lot of content editors.
Mike:
Perch users and Blog authors are very deliberately different things. Take the example of having a user who posts a load of blog posts over time and then leaves the company. You need to delete their user account, but then what would happen to their posts? Just because the user account is no longer needed, that doesn't mean those blog posts should have to change or be removed.
I don't understand where this 'related-to' keywords goes or what it would do. Could you post a new suggestion post with a worked example of what you're trying to achieve?
Where does this 'vars' keyword go? How is it different from
PerchSystem::set_vars()?+1 for Stripe Integration and a couple of suggestions following a weekend of partially successful site building.
perch_APP_custom()page function.Pete:
The second one has been done! It's in Blog now and is being rolled out to the other apps as they're updated
Good stuff! Just being able to sort by a custom date field will help a great deal with using the shop apps to sell events tickets. My temporary workaround is to insist that product codes are formatted as YYYYMMDD.
Option to bulk delete images from assets.
It takes three clicks to delete one image, then I'm taken back to the first asset screen. It's annoying when all the images I need to delete are on page 10.
At least a tick box next to each image on the page, so multiple images on the page can be deleted would be helpful.
I would like better control over the navigation menus. In my opinion the only thing wordpress does better is the navigation, you can add custom links, have items that display a dropdown rather than link to a page and lots of other stuff.
I don't use the Perch navigation at the moment as I just find it too restrictive.
A stripe app would also be cool but I see your already working on that.
Just thought of another very useful one: right now,
perch_search_form()helps you limit search to a given directory... but what if you could limit that search to a given collection instead?Shop (Stripe)
I would like to add my voice to the chorus for an update to the events app: recurring events, start and end date and time, repeating field functionality.
Also, I would like to see the members app frontend login work with the existing admin/editor backend accounts, so say staff are using Perch as an intranet they won't require two separate logins.
Thanks,
Jasper
An option in Forms to enter a comma delimited list of words to disallow (mark as spam). Eg Viagra,pharmacy etc. as well as a list of ip addresses to disallow.
To help combat hand entered spam.
User roles for collections, routes or particular collections as they are created. We work on trust with our editors, but still may be useful to protect from a potential saboteur.
Addendum I just noticed when I logged in as a non-admin user with different rights that you already have these controls built in. I see that an editor wouldn't see a collection (sample in this case is for a people collection) unless they
All these work great!
Seems like routing is hidden from non-admin users as a default too. So features delivered!
Scott, that one was easy!
The ability to move assets to another (existing) bucket, either individually or in bulk via the Assets app.
I'm looking for specific examples for the Events app here:
https://forum.grabaperch.com/forum/01-20-2015-feedback-for-the-events-app
Would love to see the ability to reply to blog comments as the author.
Import tool to help migrate WordPress sites content into collections. This would help get content out of WordPress on sites that aren't blog-like but instead use WP as CMS with meta fields or custom fields.
So a developer might build their Perch template and import into those fields like Magic.
Maybe like an Import API to import content into collections or perch templates that Perch developers can adapt client data not tied to one particular CMS such as like EE, Drupal or WP. This might be in the works as I've seen the Perch logo on GatherContent. https://gathercontent.com/how-it-works-for-agencies
As an aside with hopefully helpful background info about wrangling content in WP, I use WP Migrate DB to move content between dev, staging and production WP sites to fix urls and remove serialized content https://wordpress.org/plugins/wp-migrate-db/ and WP All Import Pro for CVS and XML import into WP https://www.wpallimport.com. Maybe some of the work could be offloaded into tools like these so core function would be to get it into Perch and developers figure out how to wrangle their data to get it ready for import. You know, more magic!
I think it would be useful to have an overview of all page titles/meta descriptions within a specific site. For example, a list view of all page titles and descriptions (possibly displayed on a single page but might have to be paginated on larger sites).
Currently, this is done on a page-by-page basis in the Page Details section but I think a "page details view" as above would give users a much better overview of these attributes for the whole site. The view could be customisable to include other page <head> section items if required.
This "By Page Details" list view could be a link on the right of By Region Type in the filter bar. Each "Page Details" item could have an Edit button adjacent to it.
Wanted to refer back to a past post in the forum about adding a <perch:notes> </perch:notes> tag block to let Perchers add info about a template for developers that wouldn't be rendered during runtime.
https://forum.grabaperch.com/forum/10-14-2014-meta-info-for-a-template
When logged in as Admin you can go into the settings under pages and check the box "hide regions you can't edit". So when the editor is logged in they might see a page called "widgets" for example but when they click on it there are zero regions. This works as expected but what if there was an option to hide the page all together if there were zero region for that editor? This would make the admin experience even more cleaner for a lot of content editors.
Scheduled tasks success message and maybe what it's done (like on the scheduled tasks page in Perch)
I get a daily email from the cron job and it would nice if it just said that it was successful and what the scheduled task did.
If you run it from the URL it's just a blank screen too would just be a nice touch to add some information there.