What I would really like is for the ID parameter to be appended to the URL and for the THEME parameter to be stored in the database. But I'm not sure how to split them like this.
My changing <fields name="request"> to <fields name="params"> I get ID and THEME stored in the 'params' but like I said, I'd like ID to be in the URL and THEME to be in the database. Hope I've made sense!!
You really don't want to have things that are part of the request in the request slider.
You can assign any template style to any menu item so it's best to do it that way rather than adding the individual parameters to manage the template. Why not make your color list correspond to template styles?
On Tuesday, August 21, 2012 11:14:34 AM UTC-4, Jedimark wrote:
> Thanks for the reply Dmitry,
> So simple!
> Is it possible, however, to have all the options contained within the same > page slider. I note creating a separate fieldset also creates a new slider.
> Thanks,
> Mark
> On Tuesday, August 21, 2012 3:46:49 PM UTC+1, b2z wrote:
>> Hi!
>> Just create separate fieldset, name it "params" and move there everything >> except ID.
On Tuesday, August 21, 2012 12:52:29 PM UTC-4, elin wrote:
> You really don't want to have things that are part of the request in the > request slider.
> You can assign any template style to any menu item so it's best to do it > that way rather than adding the individual parameters to manage the > template. Why not make your color list correspond to template styles?
> Elin
> On Tuesday, August 21, 2012 11:14:34 AM UTC-4, Jedimark wrote:
>> Thanks for the reply Dmitry,
>> So simple!
>> Is it possible, however, to have all the options contained within the >> same page slider. I note creating a separate fieldset also creates a new >> slider.
>> Thanks,
>> Mark
>> On Tuesday, August 21, 2012 3:46:49 PM UTC+1, b2z wrote:
>>> Hi!
>>> Just create separate fieldset, name it "params" and move there >>> everything except ID.
I have another question - this time concerning Component-wide default parameters. I create this parameter on a new install by adding the following in my components Manifest file:
This puts {"test":"hello"} into jos_extensions and that's great.
However I also want this parameter to be inserted for upgrades to the component. At the moment all I have is {} in the table. Will I have to run a script on upgrade to check for this or is there a better way?
On Tuesday, August 21, 2012 7:31:19 PM UTC+1, elin wrote: > I mean NOT part of the request. :P
> Ellin
> On Tuesday, August 21, 2012 12:52:29 PM UTC-4, elin wrote:
>> You really don't want to have things that are part of the request in the >> request slider.
>> You can assign any template style to any menu item so it's best to do it >> that way rather than adding the individual parameters to manage the >> template. Why not make your color list correspond to template styles?
>> Elin
>> On Tuesday, August 21, 2012 11:14:34 AM UTC-4, Jedimark wrote:
>>> Thanks for the reply Dmitry,
>>> So simple!
>>> Is it possible, however, to have all the options contained within the >>> same page slider. I note creating a separate fieldset also creates a new >>> slider.
>>> Thanks,
>>> Mark
>>> On Tuesday, August 21, 2012 3:46:49 PM UTC+1, b2z wrote:
>>>> Hi!
>>>> Just create separate fieldset, name it "params" and move there >>>> everything except ID.
On 23.08.2012, at 20:09, Jedimark <jedim...@gmail.com> wrote:
> Will I have to run a script on upgrade to check for this or is there a better way?
The way we employ in the core is that we supply the default value when get the param (second argument of the get method). This way we a also have a failsafe when something goes wrong in the database.
On Thursday, August 23, 2012 7:47:56 PM UTC+1, Rouven Weßling wrote:
> On 23.08.2012, at 20:09, Jedimark <jedi...@gmail.com <javascript:>> wrote:
> Will I have to run a script on upgrade to check for this or is there a > better way?
> The way we employ in the core is that we supply the default value when get > the param (second argument of the get method). This way we a also have a > failsafe when something goes wrong in the database.
