LazyBadger, you are the most arrogant, self absorbed and self-righteous individual I have every come across in my 30 years of being on this planet! Build a bridge and get over yourself, you are not the be all and end all of this community! Freedom of speech DOES NOT give you the right to chastise other members of this community. Are you familiar with legal terms as libel and defamination? You CAN be taken to court and sued depending on where you are in the world for comments such as you've been making about other members. Get a clue would you, they come free with a developed social conscience!

So, the issue is server side I presume.

Can someone, in polite (none-abusive) terms explain what the best course of action is in this case?

Is this a matter of changing host to a more secure one, or is it anything that we can fix on local XOOPS installs?

I would like to hear any constructive feedback on this question, but please note that abusive comments with no bearing on the problem are of no use to anyone.

(And please note - I am not a coder, I am not an apache expert, I am just a simple XOOPS user who would like a simple language explanation of the best way to prevent this happening to my own sites!)

Short and sweet and in plain english...

Please try chmod 755 on the cache/ templates_c/ and uploads/ directories. Make sure ALL files are chmod 644 except mainfile.php and any files that start with a "." Those should be chmod 444.

If your server is configured "correctly" this will work just fine. I have several sites I admin with these settings and I have 0 problems with these permissions. But then again, the hosts I use know how to configure their servers.

@LB,

Quote:

Censors?! Perhaps you need to look up the definition for Moderator. Part of our job is ensuring that posts follow the guidelines set forth in XOOPSiquette.

Exactly how many times do you have to be reminded of the terms of XOOPSiquette before you finally follow the guidelines you agreed to when you registered.

I personally value your contributions to the XOOPS community and I see you as being very intelligent and (when you want to be) a valuable contributor to the community.

On the other hand, you can be just as detrimental to the community with your constant acusations and instigations. You are a liability to the overall moral of this site. Everyone but you sees this and acknowledges this.

When are you going to get off your high horse and be a team player?

Best Regards,

James

Quote:
Did you read my answer to phppp?
I wrote "3 Steps Guide to the Complete Happiness".
It's worm, which live on local drives, and infects ALL local html-files... I think, it's something from from well-known worm for phpbb forum... Any system can be vulnerable, in depends from a lot of details

Quote:
Have and control own host. Нou must not entrust to anyone, but to yourself you can not entrust somewhat less than to the rest of the world

Quote:Well, it's not proffessional, but businessman... And let's market will be best measure - if customers use this service, it will be in the same form forever.

Quote:
Do you have another vital solution? I want to have magic bullet too

Quote:
I'm not a teacher and in not my areas I prefer to follow simple rule: "Lets' shoemaker judges not above shoes"

Quote:
Yers, but it doesn't mean, that we must have wide opened windows and doors if the battalion of the green berets doesn't guard us

short of every1 buying a dedicated server and havin full control.. what other solutions are there? not every1 can afford their own server..

so how about maybe a checksum or file integrity check on the compiled templates & cache files? when they are compiled and made, a checksum is also made and stored either in db or in file.. maybe like md5sum etc.

if the file checksum is different to the one stored when the template is compiled, then it is deleted and a new template compiled? or would that cause a major loss of speed?