-
-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Item types/titles #14
Comments
Been wondering about this too. Could well be. Two semi-related issues: the URLs for content-specific index pages are currently horrendous, and it'd be nice to optionally be able to specify a separate template and/or URL handler for those pages (so photos could be in gallery format, etc). |
I was...just learning enough PHP to try to decipher how url to page dispatch worked. I got as far as
before realizing I didn't know how to then pass in object type information. (Speaking of which, URLs like "http://s.ly/?types[]=IdnoPlugins\Event\Event" scare the heck out of me - I don't know enough to know whether there's really a way to pass in something outside of the IdnoPlugins namespace and get back data that you didn't intend for me to get, but it makes my "exposing your internals" spidey-sense tingle -- and avoiding those sorts of user worries is ...useful. |
Exactly: this is an imminent change. Those URLs are a stopgap - they're safe, but ugly, and why should the user see our class names? |
NB: I started writing docs on the wiki here yesterday, and will continue tonight, including how the page handlers and templates work. |
On Fri, Jul 05, 2013 at 12:27:35PM -0700, Ben Werdmuller wrote:
<3 |
Content plugin titles are all currently in the singular.
That makes sense for the "add some content" buttons, but less sense for the "Content" dropdown or page titles. Is the right way to fix it to add another string to each plugin?
The text was updated successfully, but these errors were encountered: