Welcome pieces of advice on com_content front overriding - Joomla! Forum - community, help and support
in short, idea implement front-end article management system authors , amdins.
the project joomla! 1.5.x platforms , should clean possible, limiting hacks as possible.
aims/targets: create article buttons users appropriate rights publish/unpublish, add front-page/remove front-page, trash, , above delete permanently. specify above because have feeling tricky part. rather not go down road "why allow delete permanently database , not go through trash", assume people give access know , primary user.
i see few options welcome input community.
if come works, i'm happy share obviously.
1. option 1 ** dirty implementation **
this heavy-duty, last resort solution: hacking joomla! core files. go if nothing else works.
the way see it, need modify relevant views, jhtmlicon class include functions, , must bypass admin side com_trash security (expecting form) way or another. variations be: custom com_trash on site side and/or adding views com_content (not sure yet of feasibility).
some ideas here: viewtopic.php?f=178&t=35240&p=1870623#p1870623
the link above not joomla! 1.5.x compatible implementation far can tell.
2. option 2 ** template override **
alright, joomla! comes nifty template override... let's use it! so, override view want (the procedure documented on website), overwrite jhtmlicon class (by calling new file, no change core, want consistent in each method). now, com_trash still issue... either bypass using form (not tested) or create new site-side com_trash (not tested) or go heavy-duty sql (not tested). not latter ones won't keep core updates... after all, sql, know application does.
i not template override option. me, illogical bind templates , components , not practical.
more there: http://docs.joomla.org/how_to_override_ ... omla!_core
3. option 3 ** plugin override **
this option most, or should if worked.
the idea load alternative com_content designed plugin callback.
explanation there: http://community.joomla.org/blogs/commu ... -html.html
i not happy storing component plugin , change should implement it.
i not make work joomla! 1.5.13 install... it's been pretty useless far.
4. option 4 ** custom com_content **
the title says all... not sure want go far... , still have com_trash issue.
5. option 5?
any idea?
thank ideas ;-)
the project joomla! 1.5.x platforms , should clean possible, limiting hacks as possible.
aims/targets: create article buttons users appropriate rights publish/unpublish, add front-page/remove front-page, trash, , above delete permanently. specify above because have feeling tricky part. rather not go down road "why allow delete permanently database , not go through trash", assume people give access know , primary user.
i see few options welcome input community.
if come works, i'm happy share obviously.
1. option 1 ** dirty implementation **
this heavy-duty, last resort solution: hacking joomla! core files. go if nothing else works.
the way see it, need modify relevant views, jhtmlicon class include functions, , must bypass admin side com_trash security (expecting form) way or another. variations be: custom com_trash on site side and/or adding views com_content (not sure yet of feasibility).
some ideas here: viewtopic.php?f=178&t=35240&p=1870623#p1870623
the link above not joomla! 1.5.x compatible implementation far can tell.
2. option 2 ** template override **
alright, joomla! comes nifty template override... let's use it! so, override view want (the procedure documented on website), overwrite jhtmlicon class (by calling new file, no change core, want consistent in each method). now, com_trash still issue... either bypass using form (not tested) or create new site-side com_trash (not tested) or go heavy-duty sql (not tested). not latter ones won't keep core updates... after all, sql, know application does.
i not template override option. me, illogical bind templates , components , not practical.
more there: http://docs.joomla.org/how_to_override_ ... omla!_core
3. option 3 ** plugin override **
this option most, or should if worked.
the idea load alternative com_content designed plugin callback.
explanation there: http://community.joomla.org/blogs/commu ... -html.html
i not happy storing component plugin , change should implement it.
i not make work joomla! 1.5.13 install... it's been pretty useless far.
4. option 4 ** custom com_content **
the title says all... not sure want go far... , still have com_trash issue.
5. option 5?
any idea?
thank ideas ;-)
Comments
Post a Comment