[Typo3-UG Australia] Breaking DB

[Paul Sanderson]

Hi Bernie,

I agree with Roger, that it's best to check the install groups first. But
it's nice to hear from other users in the same geographical area are using
Typo3. IMHO it's another golden thread of Open Source Software movement.

I run my Typo3 installations on FreeBSD webhosts, but I am familiar with
Windows (in fact have administered a few Windows server networks. The file
being reference in your error is part of the Typo Source.

Though this might not help, while attempting to secure my source recently,
I locked files I should not have using tighter permissions. I was getting
very odd errors from different scripts. Since Typo doesn't run in debug
mode by default, it wasn't telling me that I'd made some scripts
inaccessible, it just ran another script without telling me of the error,
or gave me unrelated errors i.e. the error messages were misleading.

Also check your permissions of the user the Apache & PHP services are
running under, because under Windows NT/2000/2003 server, not setting the
right security levels can also be a problem. Remember with all databases,
there are the system level security permissions on the server, and then
the database security permissions. Sorry if I'm being preachy, but even
experts (assuming you might be one) sometimes forget the simple things.

-- 
Paul Sanderson
IIC for Businsess Services
Mob/SMS: 0414183404 Email: pauls at iicservices.com

> G'day People !
>
> New to Typo3 - I d/l it a few weeks back and have taken a cursory sift
> through much of the documentation and played with the example site
> several times. I'm VERY impressed ! Powerful system and definately the
> sort of thing I'm looking for !
>
> However - I keep hitting a fundamental snag in Typo. I keep breaking the
> Database ! :( (4th time now)
>
> No specific reason, and certainly nothing techincal like manually coding
> elements. But I get errors like "can't find GIF" and "Cache not found"
> or more specifically I get this one:
>
> Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL
> result resource in C:\apache\htdocs\VRgrafix\t3lib\class.t3lib_db.php on
> line 689
>
> resulting in a borken site. This often necessitates I reinstall Typo -
> as no matter how much I try to "fix" the DB with the supplied tools - it
> inevitably does nothing :(( I've obviously checked the line in question
> - but means little to me (I'm no programmer) The more common error I
> seem to get is the cache (Why does it need a cache of the pages?) does
> not seem to accurately mirror the "real" pages. Requiring mysql manual
> fixing of the table.
>
> I've hardly put Typo3 into a "real world" scenario yet - but amongst my
> menial playing with templates and changing colours seems to break the
> system so easily - should one wonder what it would be like with a live
> website ?? Is this just me - am I doing something fundamentally wrong or
> should one treat Typo with a gentle, change one thing at a time and
> backup religiously approach ?
>
> Many thanks in advance,
>
> Bernie den Hertog
> VRgrafix
> www.vrgrafix.com.au
>
> _______________________________________________
> Typo3-ug-australia mailing list
> Typo3-ug-australia at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-ug-australia
>