simviator wrote on Aug 2^nd, 2012 at 1:35pm:

i know it looks like its not there but it is on the YaBB Quick Start Guide page for the CHMOD's "If you don't have success installing YaBB with these settings, try these Alternative CHMOD Settings."

JonB wrote on Aug 2^nd, 2012 at 1:50pm:

im sorry but i have to "The force is strong with this one." 

So its WORKING???

YAY! 

I recommend a Strongbow or Guiness! 

We still should talk (as in my, your, xnoddy's PMs).

Good Luck

Bill - I have to disagree.

There is no place I can find that YaBB tells you to change any files to '777' in sections that say (roughly) - this folder/files - here are the permissions.

That bottom part is totally generic text (copied in) and does not mention YaBB AT ALL - One of the problems with the Codex is that 'someone' included content without attribution or reference (or dates)
------------------------------------------
"2.1.1.1 Apache on Unix/Linux (CHMOD)

   * Basics
     There are different flavors of Unix/Linux - all of them share a similar, somewhat common approach. In referring to this architecture, the word "Lunix" is used for both Unix and Linux derivates. "Read" permissions apply to files that are not actively run, but only being served, e.g text or plain html files. "Write" permissions are needed to dynamically create files, modify or delete them. "Execute" permissions are needed to run executable files, for example, script files like PHP. To serve web pages that are php-powered properly, the most basic permissions that are needed, therefore, are "read" and "execute" (abbreviated as r-x).
     Possible permissions settings are:
         o r-- ... read only
         o r-x ... read and execute
         o rwx ... read, write and execute
     Needless to say, other combinations are technically possible (such as -wx, --x or -w-), but they make little sense in webserver setups and will be ignored in this tutorial."
----------------------------------------------
I will fix that with a note - but I also cannot see how anyone could read that and then infer to arbitrarily decide to make something '777' in YaBB

So I conclude you are reading things that just aren't there.

And I stand by my statement - you should not have to make files '777' on Linux/Unix for YaBB to work. I never have had to and I have worked on dozens of YaBB Linux/Unix installs. Of course, "I know what I am doing".



Edited:

Thanks again guys and yes I would indeed regard my forums as a fragile setup and that something is wrong where I've had to chmod the directories to 777.

Give it a few days and I might try chmodding back to 755 but righty now my heart can take no more stress ... & yes JonB I will listen to whet you say with all ears!

simviator wrote on Aug 2^nd, 2012 at 5:37pm:

cool just glad that we can help and you might want to make a test forum on the server and test the chmod on that 

Quote:


Can I say it would be a LOT bigger if I didn't have server problems .. no-on has been able to register for months and for years people have been complaining about not getting the email verification.

the problem is I have been on here before and got little or no support.

So I have tried hiring freelancers  -- who have messed things up like this case.
It's amazing how hard it is to find a person who can actually resolve my kind of problem - because it involves both freebsd (linux clone) server skills and knowledge of yabb.

simviator wrote on Aug 2^nd, 2012 at 7:31pm:

I feel your pain. Been there; done that.

Hang in there, enjoy your forum, and may your site's success continue. 

I get a lot of those on my testbed. In my case, the file is actually not there and Google is bound and determined to find it anyway. But in other cases, the file may have gotten corrupted or the permissions changed on it.