Right. I think those thoughts went through my mind when I made the decision
to simplify that function. Good reminder! The other advantage to having
fewer special features is there is less to document--if we ever get around
to doing that!
Cheers,
Dan
On Tue, Aug 6, 2013 at 1:52 AM, jacmgr wrot
No problem dan. I have a way to accomplish it so does not make sense to
have it in core now. In the skin that needs a special zone, just hardcode
in the zone specific for the skin. So I can use [[side.skinname]] or
[[sideskinname]] instead of just [[side]]. That will meet the need and the
z
TC+9, mz wrote:
>
>> Most possibly this is not an useful answer since I do not know exactly
>> what you want to do.
>> I use pagename.side with v4 and that works.
>>
>> Greetings, Martin
>>
>> Am Montag, 5. August 2013 15:41:42 UTC+2 schrieb jacmgr:
>&g
t; Am Montag, 5. August 2013 15:41:42 UTC+2 schrieb jacmgr:
>>
>> I can't seem to get heirarchical zones for skins to work. In version 3.5
>> I could create a side.skinname but it does not seem to work in 4.0, it
>> always uses the standard side regardless of skin. Do you
Most possibly this is not an useful answer since I do not know exactly what
you want to do.
I use pagename.side with v4 and that works.
Greetings, Martin
Am Montag, 5. August 2013 15:41:42 UTC+2 schrieb jacmgr:
>
> I can't seem to get heirarchical zones for skins to work. In versi
I can't seem to get heirarchical zones for skins to work. In version 3.5 I
could create a side.skinname but it does not seem to work in 4.0, it always
uses the standard side regardless of skin. Do you have that symptom?
--
You received this message because you are subscribed to the G
http://www.boltwire.com/index.php?p=docs.admin.performance
On Mon, Mar 22, 2010 at 4:10 PM, The Editor wrote:
> It would be a good idea to create that page, and allow people to start
> adding content as they think of things...
>
> Cheers,
> Dan
>
>
> On Mon, Mar 22, 2010 at 11:01 AM, Markus Weima
It would be a good idea to create that page, and allow people to start
adding content as they think of things...
Cheers,
Dan
On Mon, Mar 22, 2010 at 11:01 AM, Markus Weimar
wrote:
> Good decision.
>
> New user -> small site -> performance a non-issue
>
> Experienced user -> docs -> "Improving p
l make this change to the core. For both top and bottom
> zones... However, the reason I switched them from the skin was
> performance.
>
> Anytime you can put something directly in the html, rather than a
> zone, you save yourself thousands of processing calculations. Not
> only
Ok, I will make this change to the core. For both top and bottom
zones... However, the reason I switched them from the skin was
performance.
Anytime you can put something directly in the html, rather than a
zone, you save yourself thousands of processing calculations. Not
only do you have to
I just edited 'top' in a new field and went crazy because the changes
didn't show. Where did the pages top and bottom go?
Not good:
$$sitename
$$slogan
$$actions
Good:
[[top]]
Reasons pointed out in some recent post.
It will also make them show up in action zones. Muc
I've been thinking through the process of caching zones for quicker
cpu processing, and envision a process like this:
1) When a call is made to do the markup for a zone and zonecache: true
is set in site.config, then a simple check is made to see if a cached
version exists. If so, it re
12 matches
Mail list logo
