viewtopic.php?f=428&t=276192Thank you. Bookmarking this page.
Andrew (MasterChief) was giving a meeting on Joomla 1.6 where he showed what would be taken out, and what major changes were being made. I for one think reducing what Joomla already does "is_not" progress. Why is it that to have ACL you have to remove polls and pdf creation?
Honestly, the best things about Joomla are often messed up with some of the ideas that are introduced. ACL isn't needed in Joomla by default in my opinion. There are components that do a wonderful job at ACL and a component type integration for ACL is the proper way to have it implemented. Many Joomla sites are fine without having any further permission settings and honestly, bloating the code for what you can get in a component is the wrong direction. I would prefer to have Joomla slimmed down and add what is needed per site rather than have a bloated core to start with. We can only hope that Joomla's 1.6 ACL is a component type that can be eliminated and not a core function that has to be hacked on.
Doesn't make sense to me. But then again, I didn't need a back button in Joomla 1.5 until tonight and this doesn't make any sense either. Just makes for more custom modules.
Module and plugin/component creators should get started now creating what Joomla dumps in 1.6. I would start with something that allows one to disable Joomla 1.6's ACL.
In my opinion, to create a decent upcoming Joomla 1.6, all they would have had to do is add a search to the admin edit templates/css pages so you could search the templates and code without having to pull the code out and use other means. But I'm sure as this would be extremely useful that it won't be implemented. That would have been a fine upgrade. But, I am not a Joomla developer, I only use joomla 8 hours a day minimum. If I needed an ACL I couldn't get with Joomla, or for Joomla, I would be using Drupal. However, that isn't the case, and ACL for Joomla 1.5 is a non issue.
What we need is a few Joomla core developers to actually use the program, create sites with the program daily, and implement what is needed to have the editing, the creation of, and the running of such site made easier. It should be a requirement that anyone on the Joomla core development team have a Joomla website.
It wouldn't take long to get what is needed in the core, and change a few minds as to the direction this project should be heading.
Just one toggle of the words:
"Do you want to allow front end editing" yes or no <- If this exists, please do let me know where it's at. Please do. Please tell me that I'm blind and crazy. Tell me that this is Joomla 1.5.14 and that I need to study the program a bit better since moving to r1.5 versions. I can live with that. But to implement a full blown ACL without having first allowed for this sort of implementation is, well, not very helpful.
That along with a search function for the templates and css, would be a far greater feat for those that use this program day in and day out than an ACL that won't solve all the issues and needs of each site administrator.
Next thank you and rant.... Joomla 1.6.. Where are the polls? Where is the pdf button? Why on earth can I still not search the templates and css without taking the code out to an external editor . And of course, where is the toggle for disabling front end editing? Might as well ask now, because past experience back to Mambo proves that the core team would rather look good and chase after what others do, than to fix and do what is actually needed to produce results that work for end users, results that help those that use the product. Would be better to win another Open Source CMS award. Correct?
On to implementing a back button that I had no issues with in 1.0 Joomla. It might even be there for all I know, but it's not working right with the current template if it is. Thanks, and have a great evening.
