Menu

#64 forum title description is not getting stored inDB

Fixed
None
Medium
Defect
2019-07-02
2015-01-06
Anonymous
No

Originally created by: drop2sac...@gmail.com

What steps will reproduce the problem?
1.redeploy the war, then you ll have to re-configure your forum title, meta tags , name etc.
2.
3.

What is the expected output? What do you see instead?
These info should be persisted

What version of the product are you using? On what operating system,
database, and application server/servlet container?
* Product: JForum 2.3.4
* OS: linux
* DB: mysql
* AP:

Please provide any additional information below.

Related

Wiki: NewFeatures270

Discussion

  • Anonymous

    Anonymous - 2015-05-07

    Originally posted by: ulf.dittmer

    While it would be nice to persist these in the DB, I'm guessing that is some time off. Until then, make sure you keep the WEB-INF/config/jforum-custom.conf file before deploying a new version - the settings are stored in there.

     
  • Ulf Dittmer

    Ulf Dittmer - 2018-09-19
    • status: New --> Fixed
    • assigned_to: Ulf Dittmer
     
  • Ulf Dittmer

    Ulf Dittmer - 2018-09-19

    A backup of the configuration data is now stored in the "jforum_config" table in the database.

    Before an update, the jforum-custom.conf file should be backed up so it can be restored afterwards. If for some reason no copy of the file is available after an update, a fresh copy can be created from the table via a SQL command like

    select config_name||'='||config_value from jforum_config

    or

    select concat(config_name, '=', config_value) from jforum_config

    or something similar, depending on which database server is used.

     

    Last edit: Ulf Dittmer 2018-10-04
  • Ulf Dittmer

    Ulf Dittmer - 2019-02-13
    • status: Fixed --> Accepted
     
  • Ulf Dittmer

    Ulf Dittmer - 2019-02-13

    This change has been commented out for the time being (in SystemGlobals.saveInstallation), and will be re-enabled in a later release. It requires lengthening the jforum_config. config_value field; it curently can't accommodate long property values (like database.connection.string for MySQL).

     

    Last edit: Ulf Dittmer 2019-02-13
  • Ulf Dittmer

    Ulf Dittmer - 2019-07-02
    • status: Accepted --> Fixed
     
  • Ulf Dittmer

    Ulf Dittmer - 2019-07-02

    This has been fixed in the trunk.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.