[TYPO3] CSS woes

[Patrick O'Hara]

I prefer CSS styled content, but I have yet to get a straight answer on what
that means in Typo3.  This is the root of my issues with Typo3.  I like
having options, and Typo3 is a great platform.  I don't know that I am
"giving up".  What is comes down too is that my job is to coordinate the
content of our church website.  I was picked because we can't afford to
higher someone to do it (it is a church after all).  I picked Typo3 so I
wouldn't have to stay up till midnight making changes to static pages.
The issue I have is that I find myself staying up till midnight to create
valid HTML and figure out which extension is causing my problem.  The reason
I am ready to "give up" is because I have other things to work on, like
content.  Ultimately I have already spent way too much time (about 10 man
hours) to get the page as valid as it is now.  I need to focus on fixing the
CSS for the page (which came from an elder in the church :-).  I thought a
good way to start was to ensure that it was valid.  The HTML turned out not
to be valid, so I started there.  The HTML is now "valid" even if it is not
what I want.  So I can get back to CSS, so I can get back to content, which
by the way, is what I get paid for.  Not that I get paid :-).
I guess I am frustrated with the position I find myself in.  It's not Typo3,
or the communities fault.  The attitude I keep running into on this list is
that I should be able to spend hours looking at this setting and that
extension in Typo3.  I don't have that kind of time.  That is why I am using
Typo3.


Seriously thanks for all the help.  I really do like Typo3 especially
because of people like you who help me not spent days, I just wish I didn't
have to spend so many hours.

--
Tanks for your Support
Pat O'Hara
  _      _      _
/*\==  /*\==  /*\==
<ooo>  <ooo>  <ooo>

On 3/9/06, Christopher <bedlamhotel at gmail.com> wrote:
>
> Hi,
>
> On 3/9/06, Patrick O'Hara <pdohara at practicalprogrammer.org> wrote:
> > See Below
> >
> > On 3/8/06, Christopher <bedlamhotel at gmail.com> wrote:
> > >
> > > Hi,
> > >
> > > On 3/8/06, Patrick O'Hara <pdohara at practicalprogrammer.org> wrote:
> > > > Thanks for the response, but no I do not have a meta tag in my
> template.
> > > > Something in Typo3 is generating the meta tag.
> > >
> > > I've never seen a 'us-ascii' charset meta element in a typo3 site.
> > > I've hardly ever seen us-ascii specified as a charset in _any_ website
> > > in fact. Typo3 will add _one_ meta element specifying the iso-8859
> > > charset by default, it will _not_ add that second one--it has to be
> > > there as a result of one of only four things that I can think of:
> > >
> > > a) If using TV, it's in the original template and you've selected it
> > > when mapping the template
> > > b) You've specified it using "page.charset =" (though I still don't
> > > know how that could get you _two_ specified charsets...)
> > > c) Possibly an extension put it there (but this would be a strange
> > > thing for an extension to do...)
> > > d) Maybe it's there because you're using one of the deprecated static
> > > templates in your main TS template (if so, switch to css-styled
> > > content instead).
> > >
> > >
> > > -Christopher
> > > _______________________________________________
> > > TYPO3-english mailing list
> > > TYPO3-english at lists.netfielders.de
> > > http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
> > >
> >
> > Here is what I have.  Perhaps you can see something here that looks odd.
> >
> [snip]
> >
> > I have no constants defined.  I have the following static includes:
> > styles.content
> > content
> > cSet stylesheet
> > cSet
> >
> > and I have these static includes from extensions:
> > CSS Styled IMGTEXT
> > CSS Styles Content
> > HTML/CSS Styling
> >
> > If there is anything else you would like to see let me know.  I am
> pretty
> > much ready to "give up", and live with the fact that Typo3 is creating
> an
> > invalid page.
>
> Why are you ready to give up? I suggested four possible places where
> such a thing could possibly  come from, and while you've ruled out (a)
> and possibly (b), there are still (c) and (d) to consider. Try
> removing each extension in turn and regenerating the page. If it's
> still there, the most likely candidate will be one of the static
> templates--get rid of those and use css-styled-content instead!
>
> -Christopher
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
>