> The backend-form for content-items does not contain fields, I could
> missuse and I'm not very happy with telling the editors that they
> should not use the datefields, but use other fields as date fields.
These fields are NOT date fields but responsible for "release time" and
"expiration time"
Hi,
thank you for your reply.
> Out of the box you can just get the items with appropriate start-/endtime
> settings, since both fields belong to the so called "enable fields".
Yes, I know.
My question is: is it possible to NOT use the enable fields for certain FE-page
like the backend does.
> What I did not found out yet:
> - how can I fetch content-items without caring about start- / endtime
> like the backend uses on preview pages - or more precises: I have
> content items in a sysfolder and several pages that use this folder.
> So most pages should respect start- / endtime, but oth
Hello,
thank you for your attention.
> > But if I add something at location 5 or 20 it comes once a page before or
> > after all content-pieces.
>
> I personally don't understand what what the problem is. Can you try to
> rephrase it or state what are the current results and what are the
> expec
>> But if I add something at location 5 or 20 it comes once a page
>> before or after all content-pieces.
>
> I personally don't understand what what the problem is. Can you try to
> rephrase it or state what are the current results and what are the
> expected results?
I guess it's about the diff
> But if I add something at location 5 or 20 it comes once a page before or
> after all content-pieces.
I personally don't understand what what the problem is. Can you try to
rephrase it or state what are the current results and what are the
expected results?
Tomas Mrozek
___
Hello,
the basics of my site are working so far, but I did not get into content
handling.
My content is added like this:
subparts {
DOCUMENT = COA
DOCUMENT {
10 = CONTENT
10.table = tt_content
10.select.orderBy = sorting
}
}
which works for most pages.
But if I add something
