|
You are here: Home / collection GUI abstracted
collection GUI abstracted
Forum /
Feature Requests /
collection GUI abstracted
Reply
Subscribe
Start new thread
Syndicated Feed (RSS)
|
Displaying 1 to 3 of 3
|
Previous
1
Next |
| Author |
Message |
wisecounselor
Posts: 255
|
|
collection GUI abstracted - Posted: April 29, 2008 - 10:20 AM
|
Quote and reply
|
Not sure if that is the right term, but I'd like for the generic collection manage interface in the cms to abstracted out somehow, so it would be easy to not only create my own collection, but create a custom user interface for the data management, somethings the table-based interface just isn't applicable.
Or some way to easily override the interface so the cms loads a custom front page for the collection.
I realize the intent of the collection setup is to quickly drop in new content types, versioned or not, which is cool, I would just like more code-level interface control rather than configuration file control.
|
|
Back to top
|
|
lux
Posts: 645
Location: Manitoba, Canada
|
|
Re: collection GUI abstracted - Posted: April 29, 2008 - 11:37 AM
|
Quote and reply
|
wisecounselor said:
Not sure if that is the right term, but I'd like for the generic collection manage interface in the cms to abstracted out somehow, so it would be easy to not only create my own collection, but create a custom user interface for the data management, somethings the table-based interface just isn't applicable.
Or some way to easily override the interface so the cms loads a custom front page for the collection.
I realize the intent of the collection setup is to quickly drop in new content types, versioned or not, which is cool, I would just like more code-level interface control rather than configuration file control.
Typically, what I do when I need a custom interface is generate something in the Tools menu. You can set a box to be called there in the app's conf/config.ini.php file with these settings:
app_name = App Name
admin_handler = admin
admin_handler_type = box
This will call your app's boxes/admin/index.php when you access it through the Tools menu now. Because that's most likely for admins only, you would also want to make sure there's an access.php in boxes/admin/ as well with something like this:
sitellite_access = private
sitellite_status = approved
sitellite_action = on
sitellite_template_set = admin
sitellite_goto = cms-login-action
That will show it using Sitellite's "admin" templates so it matches the back-end look, and keep anyone who isn't a site editor out.
Hope that helps.
Lux
|
|
Back to top
|
View user profile
Contact this member
|
wisecounselor
Posts: 255
|
|
Re: collection GUI abstracted - Posted: May 8, 2008 - 4:58 PM
|
Quote and reply
|
This is similar to what I've done as well, I'm just trying to figure out the simplest way to create new content types with versioning. Maybe your method is the best, I'll just have to figure how to to make versioning work in my own app / forms.
I'd also like a copy of the site user admin tool so I can give a member the ability to add users without being able to login to the overall cms admin. I've done it before, but it seemed like some needless hacking to get it to work, if the sitemember app could have some level of configurable control like this... just thinking out loud, so to speak
lux said:
wisecounselor said:
Not sure if that is the right term, but I'd like for the generic collection manage interface in the cms to abstracted out somehow, so it would be easy to not only create my own collection, but create a custom user interface for the data management, somethings the table-based interface just isn't applicable.
Or some way to easily override the interface so the cms loads a custom front page for the collection.
I realize the intent of the collection setup is to quickly drop in new content types, versioned or not, which is cool, I would just like more code-level interface control rather than configuration file control.
Typically, what I do when I need a custom interface is generate something in the Tools menu. You can set a box to be called there in the app's conf/config.ini.php file with these settings:
app_name = App Name
admin_handler = admin
admin_handler_type = box
This will call your app's boxes/admin/index.php when you access it through the Tools menu now. Because that's most likely for admins only, you would also want to make sure there's an access.php in boxes/admin/ as well with something like this:
sitellite_access = private
sitellite_status = approved
sitellite_action = on
sitellite_template_set = admin
sitellite_goto = cms-login-action
That will show it using Sitellite's "admin" templates so it matches the back-end look, and keep anyone who isn't a site editor out.
Hope that helps.
Lux
|
|
Back to top
|
|
|
|
