Hi,

I have a very big database migration ahead of me regarding a really old version of JForum.
Old version: jforum-2.1.4
New version: jforum-2.8.3

Are there any upgrade DB SQL scripts available for the JForum database that I can execute one-by-one to get up to the latest release (I am using MySQL)?
There are many releases to go through to upgrade, so it would save me a lot of time if you already have the required scripts available/collected.

Any help/suggestions are appreciated.
Thank you!

Regards,
Tommy

Ugh, 2.1.4 is seriously outdated. But I'm happy to hear that even after all that time, JForum continues to be useful

To my knowledge, no such script exists. You'll have to go through the scripts in https://sourceforge.net/p/jforum2/code/HEAD/tree/trunk/upgrade/ one by one.

You're bound to bump into some issue or other, but feel free to come back here with questions, and we'll try to help out.

Perfect!
Just what I was looking for, but didn't know where to find.

Thank you so very much for that.

Btw, extra thanks for a quick and competent reply.

- Tommy

You can find the DB schema upgrade scripts under the upgrade directory. The subdirectory name is for the new jforum version where database schema is also changed. So, you'll need to go through each subdirectory from 2.1.5 to 2.8.0.
Using this as an example for mysql:

mysql -u USERNAME -p DBNAME < 2.1.5/mysql_2.1.4_to_2.1.5.sql

The migration went well! The only problem was that the older scripts contained "TYPE=InnoDB". But when changed to "ENGINE=InnoDB", they worked fine as well.

Everything looks ok. I can login as admin and see all registered users etc.
But the "Forum Index" list on the main page is empty. They are correctly stored in the database tables though.
I did a "SELECT(*)" on the following tables as well:
jforum_categories = 1
jforum_forums = 4
jforum_posts = 285
jforum_posts_text = 285

Can you suggest anything for this?

I get no error messages in Tomcat or in the web page.
Is there any way to debug this? The problem is very shy and quiet.

Thanks!

Edit:
Added jforum log file as attachment. But it doesn't say much unfortunately.

I am using:
openjdk version 11.0.16.1
JForum version 2.8.3
Tomcat version 9.0.82
MySQL 8 version 8.0.34
mysql-connector-j-8.1.0.jar

You may try to disable cache by adding the following setting to jforum-custom.conf and see if this works

#########################

# Topics, Posts and Cache 

#########################

topic.cache.enabled = false

posts.cache.enabled = false

Thanks for the advice.
But unfortunately it didn't solve the problem.

Another strange thing is that when I go to the search page and enter any search term, then I always get "0 records were found" even though I use terms that I know exists.

Any other suggestions I can try out?

Edit:
I connected JForum back to the new database (the one that was initialized when I installed JForum version 2.8.3) and here it just works! I can in the Forum Index list see the "Category Test" -> "Test Forum" -> "This is a test forum"
But when I connect JForum to my migrated database, then the Forum Index list is empty again. Seems like something is missing in the migration steps.

Maybe you need to reindex all your posts. You can go to the Admin Control Panel > Lucene Statistics > Recreate Index

It did not solve this specific problem, but now the search functionality partially works.
When I search for a common term, I get the following response:
"Search Results: 222 records were found"

But below the "Search Results" it says "No results were found. Click here to make a new search. ".
Also, the Forum Index list on the start page is still empty as well.

What a weird problem.

Any other suggestions to share with me?

You may try to change the Permission setting for each User Group.
https://sourceforge.net/p/jforum2/wiki2/Permissions/

If you can provide some screenshots, it would be helpful.

OH YES!!

All groups (including "Administration") apparently had their group permissions set to negative selections ("Allow all" deselected, and "No" set for all choices). Probably due to safe guard settings when changes was made to groups/permissions in a newer version of JForum

Now it just works!

Thank you VERY MUCH for your help in this matter!
Wish you a great Sunday as well.