Joomla! and Beyond 2013

Módulos con permisos y edición frontend

Randy Carey  · 


Extracto de la transcripción automática del vídeo realizada por YouTube.

when they click the edit button we get a little dialog box like this prompting them just for the information that they need in order to make that update on that module imagine also on the restaurant that they want to update some of the event information maybe

they aren't changing the information but they want to change the way it's being displayed for instance on the the call-out date information maybe not they don't always want to say the next item here but they got this really big thing coming up

in two weeks and they want to be able to tag it and force that one to the top so by going like before they be able to see an edit button they click and they have just the options they want to show the neck they want to show a summary on this or not do they

want to go to the next one or get the next one by tag or show both and what is the tag they're going to use something very simple and very basic and intuitive for a non technical user say they want to look at the different listing of events coming up the

same thing they have an edit button here by clicking on the edit button a little dialog box pops up and they can change just the details that matter like the account the category the date range the formatted in the month day and month all they want to link

the titles all those sorts of things let's say you have another employee and this employee doesn't have the same privileges with this employee when this when clicks gets a very a subset of what we saw previously based upon that particulars that person's

particular assignment to a role this case he can turn on and off link titles whether you want to show the number of hits per item and whether or not you're showing intro text modules with permissions in front and editing I try to show you just the idea

of what I think it is what it involves I'm with Randy carry from the states I work developing websites for different clients and also I'm trying to shift more to the development area under the IQ project where the idea is to make improve the CMS user

experience that's where the ICU e comes from improve the CMS user experience so we give our clients a user experiences that's easier than what we use as a developer give them more of a streamlined back end and then I've listed several different

ways that we can improve the user experience and in this particular talk we're focusing mostly in the front end editing role-based ACL a little bit of that as well so I've already shown you the imagined section imagine what it front and editing should

be like four modules and let me also give a footnote that I know that on previous talk they said that they're talking about adding some module editing and that sort of thing in joomla this is my own project I spun off and work these are my own ideas I

don't know if the if the regular joomla project is thinking particularly how they're going to do it yet just that they want to so just realize that this is my own view and implementation of how I do it I want to give a little bit of presentation on

front and editing the philosophy of it why it has value and what things maybe shouldn't belong in the front and editing I'll talk a little bit about ACL permissions because if we do front and editing we have to set up permissions to say who actually

can edit the modules how our modules different from components they are different and that means the way we edit in the front end is going to be different than the way we edit components on the front end and when we set up permissions there's things like

called actions and modules have their settings and we have to set up things like you know what we sort of create edit delete we might have formatting or display or list settings that goes to each module and how do we tie them to the different fields that we

allow and which fields do we want to provide in the front end I'll give a quick demo on how to implement this and I the code I thought when I came here was going to be something really short and simple it turned out it took a lot of work to get this done

so I don't have it all completed and I will if you go to the iCube project com just sign up here on the side and I'm just not a spam list just want to physically give you information and this is the project I'm working on and here you can download

this code is available now that sort of thing at the end I'll give a quick little demonstration I don't have a lot of time but i'll try to squeeze it in one thing i wanted to start out though before i go into the next phase is i gave this presentation

i propose this presentation in the middle of april for jab and got accepted and beclan I've is giving presentations on ACL and role-based ACL I use diagram to explain the ACL and I say if you notice look at everything uses access levels you've got

the components the modules the menu items the plugins they all refer to access levels but when it comes time to permissions only components use permissions modules could use permissions but they don't and it's true they don't and I thought it'd

be rather easy so I thought I'll put together presentation showing how you can use permissions on modules and how you can apply them for instance friend and editing after I got my proposal accepted i started doing the work and realized joomla core does

not anticipate that modules will be edited anywhere besides module manager and it didn't try to stop me from doing it but all the things that does to help have a CL implemented and forms implemented for components those things just aren't there for

module so I had to do a lot of extra work around and code around it took more work than I thought it was going to to get to the point I got to but I did get there I just need to do a little more testing before I'm able to release it so front and editing

I think it's a little philosophy on this we have to realize that we as developers and site implementers realize all the parts that go behind a CMS in the templates the components plugins and what they do and how they how they interact but with the people

who use our websites who commissioned it those people who maintain the content they have they realize it as a series of pages or as a particular page with different parts on it what we do quite often as we impose upon them in order to manage this website you

have to understand what we understand and that's more complicated than they probably need to know if we realize that the users approach a website based upon the visual mental model of that front end and we can met we can map a lot of the editing to that

we've made their job a lot easier and more intuitive we've built a much better product if we could think of that if we get them to think of it in terms of pages and parts on pages on the front end we already have editing of components that falls right

and place the component and sets it in but we don't have it for modules yet it'd be nice if we could have somebody go in and edit things like what items i'm going to put in a rotation and what texts do i put in with that a list what items they

want to put in this list what i want to turn on feature do i want to change the category those sorts of things and all the different call-outs all these are modules it'd be nice if they could just click on those this is my view of what front and edit II

should be like this restaurant for instance is like you want to change the contact information you login if the person has rights is a little icon they can click on it and edit that information they can click on and edit the leading information for this particular

menu and maybe the person only is going to be changing prices we're going to manage the menu somewhere else the different items in it but as far as changing prices they get a list here and they can click here and change just those particular prices that's

[ ... ]

Nota: se han omitido las otras 3.891 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.