Troubleshooting vbulletin

[Mohammed]

Common errors and solutions in vbulletin (5.5.x)

In several instances, I would have no other choice than removing the forums and reinstalling it, using a backup and causing lots of inconvenience to users. This is why this thread now comes to document certain lessons learnt in the process, through in the hard way.

0. Lesson zero:

In fact, I passed at this stage. After buying my vbulleting license, the first thing to do was to go shopping for a hosting service. I searched many websites and looked for tips about everything. Many hosting services provide very cheap services, but luckily I got very informed about what needs to be done to host the forums. In particular, I had to answer the following questions:

A- Which is better Windows or Linux environment? My choice (after searching for the answer) was: Linux

B- Do I have the capability to install the forums? The answer at the time was 'definitely no!' I searched for a hosting service that does that for me.

C- Is any hosting plan good for me? My answer was: sure! That was a mistake. The first hosting service I used was horrible and I had to leave it and for another one. I finally managed to grasp some of the technicalities of: bandwidth, cpu cores, disk space, etc.

1. Make changes to the forums files

on the server rendering errors in browsing, posting and doing other stuff in the forums. Lesson: Always copy the folder of the forums before making any change to its folders.

2. Inadvertently delete the database (SQL)

or making changes there rendering errors in the forums. Lesson: Minimise tampering with the SQL and only do what I am 100% sure is safe to be done. Keep a backup before doing anything. Ask the host to fix an SQL error for you.

3. Files on the host service get corrupted

or compromised by hackers. Lesson: Always keep a daily backup through the host service. Download to my computer a weekly backup.

4. Changed the URL of the forums

inside the cpanel rendering the forums inaccessible and had to reinstall it. Lesson: Ask experienced people about things you want to change which you are not sure of.

5. Deleted an entire topic instead of a post.

Lesson: always use soft deletion first before permanently deleting the posts.

6. Waste time in deleting inactive members.

I do not want such users to be listed as 'banned'. Lesson: Rename the banned user group to 'inactive members' and create a demotion criterion under the Promotion option whereby members inactive for a specified period of time are automatically moved to that group. You need also to set the group as not a banned group (there is an option which says: this is not a banned group Yes/No). Otherwise, inactivated users will receive the message "You have been banned by XYZ")

7. Uploaded smilies t

hat I found in other forums and found after the upload that many of them are indecent. Lesson: Always check pictures or smilies before I upload them.

8. I installed a third-party plugin

or product and errors happened. I uninstalled the plugins and the errors persist. Lesson: Copy the forums folder before adding third-party plugins.

9. Minor issues

happen such as a blank page popping up in the login panel, clicking a post renders an expired search result issue or invalid security issue, etc. Lesson: minor issues can be solved through the diagnosis section in the admin cpanel. Such functionalities should be understood.

10. After a year or so, I discovered that I had made

unnecessary groups of users

and my channels are not optimally organized. Lesson: think carefully about the needs of users and tweak settings as the need arises. Naturally, the evolution of the forums will show new needs, but if I had the chance of going back to the past, I would have not changed anything with the user groups until I would be precisely clear about what really needed to be done.

11. I changed the PHP version

haphazardly (moving from a version with say a number 1 into 3 is tempting!) but the forums went down. I reconfigured the PHP but still the forums did not work and I had to go back to the host service. Lesson: Never tamper with the PHP unless after I ask experienced people.

12. Upgrade or installation failed.

Lesson: If unsure of how to install or upgrade, go to the hosts. Their experienced staff should do it for me.

13. One issue unsolved.

This relates to the way in which I can bring in as many

active

members as possible. People on the social media prefer to send private messages than discuss their issues publicly. They prefer to read posts than react to them. This is what the majority of newbies do in my forums. I am still navigating my options but for the time being, any newbie cannot access my translation courses unless they make a contribution. New starters have their first posts moderated. This problem (as I saw in several other forums) is common and, for me, the solution is too far to reach.

14. Deleting style problem.

A style (not an important one) got defective and I chose to remove it. Not being aware of technicalities, I just clicked 'yes' and save etc. The result was that the homepage turned blank without any module that used to be there. It turned out that when deleting the style, the homepage had already been affected by that style and by clicking yes at a certain stage, it meant I approved the homepage to be affected by deletion. To solve this problem, I had no choice but to edit the front page and re-insert the modules.

Lesson:

be cautious when deleting styles. Do not click yes at the prompt that tells you all other styles using the shared page will be affected.

15. Disable the 'like' option.

The purpose of my forums is for users to be intensively engaged with certain educational tasks. In often times, users have been using the 'like' feature as if they were in the social media! The 'like' option, from my perspective, is to serve two functions 1) to boost the reputation of a user so that at a given point, he can be automatically upgraded into another user category, and 2) to indicate to others that the solution offered by a specific member has been proven to be efficient as regards a given problem that other users may have themselves.

The misuse

of the 'like' feature led the users to be extremely inactive. They just think they have done a great thing by liking a post. But, I want them not only to be active but to offer constructive contributions. This is why

I disabled the 'like' feature

in my forums.

16. ckEditor crashes. Error reads: There was an error loading the rich text editor. You may use the plain text editor, or you may reload the page to try again. If the problem persists, please contact the administrator.

Solution: Solving this problem requires two steps: STEP1: Since the editor is a javascript applicaiton, it means the error has happened because of syntax error. In my case, I was tampering with the font families in the js folders belonging to the editor. STEP1 therefore is to restore settings to their original configurations, so that you eliminate the error STEP2: This is problematic. What happens is that the syntax error sticks to the chache memory of your devices. It is highly likely that even after you solve the core issue (syntax error), users of your forums will still see the error. Since the ckEditor is a javascript application, then 100% it runs on users' computers, not your server. To solve this problem, every user must free the cache memory of their own devices. Sometimes, they have to give up on a given internet browser and use another one. Frankly, this error is a nightmare for me.

17. It is possible to change the color of member's username in the postbit section. You can change the color, emphasis (bold) etc. Follow the thread in Vbulletin https://forum.vbulletin.com/forum/vb...in-appear-bold

[Ahmed Magraalneel]

Did you consider using the PHP forums like this https://www.phpbb.com/? It could be more stable than vBulletin.

[Mohammed]

vbulletin is very stable and secure. The problem is with the modifications (third-party applications). I am looking for a developer to take over the installation of the mods. The current issue is with Metro style. it should be updated to v.1.1.5 but the update has messed up everything! That is one reason for us going back to Nov 26 backup.