Welcome to the Question2Answer Q&A. There's also a
demo
if you just want to try it out.
Login
Login
Register
All Activity
Questions
Hot!
Unanswered
Tags
Users
Ask a Question
About
Wiki
Welcome to the Q&A for
Question2Answer
.
If you have questions about the platform,
click here to ask
and please use English.
If you just want to try Q2A, please use the
demo
, which also grants admin access.
Apr 29:
Q2A 1.5.2
Related questions
How do I upgrade to 1.4?
What key files should I change to move around and add graphics that aren't in the main CSS file?
Is there a tutorial on what files to change for the theam (colors & style)
Error when upgrading database to latest version
I've upload the files to the server - but it hasn't changed - now what? ehowdoi.info
after updating Q2A to new version what will happen to edited language files in older version
Please, what are the latest files that have been updated in the last release?
What Are The Initial Q2A Core Files That Need To Be Loaded
what happens when you flag an answer or question as an admin?
what will the next version include and when?
All categories
Q2A Core
(3,252)
Plugins
(356)
What files change when upgrading ?
+1
vote
HI
What files I should change, when upgrading from 1.2 to 1.2.1 I can't overtwrite all files becouse I changed some of them.
upgrading
asked
Aug 14, 2010
in
Q2A Core
by
marcin1
Please
log in
or
register
to add a comment.
Please
log in
or
register
to answer this question.
2 Answers
0
votes
To upgrade from 1.2 to 1.2.1, you can delete all old files (1.2) including qa-config.php file, copy new files (1.2.1), rename qa-config-example.php (new one) as qa-config.php and edit this file by adding the database details (in the new qa-config.php file). You can do the custom changes in other new files. You can use a file comparison software, if you have forgotten the changes you made.
answered
Aug 14, 2010
by
Katte
Please
log in
or
register
to add a comment.
0
votes
The problem with a file comparison though is that it will also show changes made in the regular codebase. If a lot of changes have been made it will be a nightmare.
I would recommend getting a fresh copy of 1.2 and running a diff to find all your changes. Then mark them in your code base (maybe use a special comment like /**EDIT: description */ ). Then start afresh with 1.2.1 and copy your marked changes to the new codebase.
In future I would suggest setting up an advanced theme and making as many changes as possible in there. You can use variables like `$this->template` which tells you the section you're on. I just upgraded from 1.0 to 1.2.1 and managed to put every change in the theme.
answered
Aug 15, 2010
by
DisgruntledGoat
Please
log in
or
register
to add a comment.