After solving couple of times the "500 Internal Server Error" problem as described in a previous post, I received another complaint from one of my clients I host:
"I also cannot save the articles and here is the error I got
500 - An error has occurred!"
Easy cake - I was thinking, but after checking his account, discovered, that all settings described on that article (namely the collation settings in database) where correct.
Like the majority of web developers I develop my websites and services locally before Ipublish them on the Internet. This makes sense in a variety of ways, from saving a lot of bandwidth to faster updating or improved security.
One of often overlooked security (and not only) resource for any Joomla site is under your fingertips! With each Joomla install (even from the old Mambo days) you have a file named htaccess.txt in your site's root directory. In most cases is never touched, and left as is - most weekend webmasters don't even know what is for. A few are using it to help Joomla or the specialized SEF URL builders to make those pretty SEF URL's for their site. And that's pretty easy - in most cases it's enough to rename it to .htaccess, and you are set. But there is much more power hidden there...
Full Path Disclosure (FPD) vulnerabilities enable the attacker to see the path to the webroot/file. e.g.: /home/omg/htdocs/file/. Certain vulnerabilities, such as using the load_file() (within a SQL Injection ) query to view the page source, require the attacker to have the full path to the file they wish to view. Then the attacker can use this info to perform other type of attacks based on the obtained information.
This is a two step process, and here I'm assuming that you are clever enough and you are hosting with a company that offers cPanel . On other hosting environments the process might be slightly different, but the basics are the same.
Even if hosting Joomla on GoDaddy can be challenging, and anybody ever built a site on their servers will tell you to turn to some better Joomla host, many people still choose them because of the excellent price/offering ratio. Here are a few tips that will help you get Joomla running on GoDaddy with minimum fuss.
JA's K2 Search and Filter add-on is a nice - and powerful tool. But has an annoying problem (at least in version 1.0.7): When one edit a K2 item which have extra fields, on save an ugly error 1062 database error is popping up. The component is working correctly, the modified date is saved, but the user doing the update gets seriously confused.
As I said elsewhere on the site one of key issues of running Joomla on a Windows server is to understand and apply correctly the Windows files and folders permissioning system to your Joomla install. Instead of writing my own compilation of how-tos, I reproduce here the excellent tutorial written by Russell Winter on the Joomla tutorials site. All kudos are going to him!
For those of you that are either developing or delivering your Joomla! Web-Sites from the Windows environment, it is sometimes difficult to obtain relevant information regarding permissions. Unfortunately, it is a fact that most Web-Serving is offered under Unix and that Unix is pretty well documented within this environment. Hopefully the following information will go some way to clearing up any confusion and provide a little guidance.
It is an error which drive me crazy couple of times. It's easy to fix - but hard to detect why happening. I didn't see any good explanation which fits to each single situation I needed to handle it. There are couple of popular theories on what causes the "jtablesession::Store Failed - DB function failed with error" type of errors, but sincerely I can not confirm any of them:
Recently - once again - I faced a very annoying problem: after migrating a Joomla site from Joomla 1.5 to Joomla 1.7 - and later to Joomla 2.5 - time-to-time the menu ordering switched back to the essentially wrong ordering resulted from migration process. First time I thought I am doing something wrong, and when my client cried about, I reordered a menu again and again. I have to fight with this problem too many times until I found the source of error and an easy fix.
Joomla supports out of the box the UTF-8 character encoding, so someone building a multilingual website should not have any problems using UTF-8 character encoding in his site. Right?
Yes and no, the CORE Joomla is problem free as I write this, but some non-core add-ons, templates - and yes, your own, home-cooked code can produce garbled output. Let's see why, and how we can fix it!
If you search for the title of this tip you will found lot of hits. Actually, my last search returned 6.6 millions of hits! Apparently lot of people are having with - or has fears on this subject. When I first published this tip, back in 2005, there was no such amount of answers/references, and I think, that this real flood of sites about this potential issue is not because lot of people would having problems, but because more and more people are getting into building interactive sites.
So, do You have problems?
There are numerous other tactics that can be used to break into a computer system, and these usually involve discovering weaknesses or loopholes in the server software's defenses. When a programmer writes software that runs on a web server, he tries to make sure that the software cannot be abused - but it can be very difficult to foresee every eventuality; vandals and hackers are always pushing software to the limit and trying out operations which the software was not designed to handle, in an attempt to discover a way in.
Yeah, you may say that nothing coming out from that Redmond-based factory does not qualify as LAMP environment, and Joomla is built yo be used on LAMP servers, am I right? Yes... and no. Why not let them to play with the best CMS around .
So, what a Windows aficionado should know if wants to run Joomla on his favorite server?
Did you ever get this annoying error?
Save failed with the following error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 SQL=INSERT INTO ***_contentitem_tag_map
When a registered user adds a new entry in your SobiPro powered business directory in your Joomla site you might want to add a link pointing back to his Community Builder profile. Sounds simple... but the powerful templating system of SobiPro might be cryptic even for advanced users. And you might not have a membership in SobiPro club - BTW, worth every penny!
Here is one way you can do this!
One popular and potentially devastating method of attack against Joomla powered sites is SQL injection. Any web application that makes use of a database usually communicates with the database for necessary functions using a special language known as 'Structured Query Language', or SQL. Joomla, by the way, uses an open source implementation of this language, MySQL.
You may already seen this annoying message instead of your Joomla site:
And you are virtually clueless what to do about, and even the smallest bit of info on what happened can be a lifesaver.
Over the years spent in web page building and maintaining (since 1995, when published my very first webpage on a self-hosted SCO Linux box) a lot of information has been collected, settled down and at the end the best and most important tricks helping to make a website became fast and stable in the same time where surfaced. Despite the fact, that I wrote about this subject several times, it's a subject wich never looses his actuality.
Web Links 13
Articles View Hits 1983853
Currently are 103 guests and no members online