I'm on 1.3.9 now and am looking at the 1.3.10 install - downloaded the latest copy this morning - and am reading the UPGRADE document... it has the comment about
mysql:
ALTER TABLE page CHANGE id id INT NOT NULL AUTO_INCREMENT;
I'm using mySQL and want to do the upgrade but I'm also wanting to make sure that this won't hurt my 1.3.9 users as I'd like to leave them running that version until I'm sure I'm ready to implement the 1.3.10 version...
Will doing this mySQL change hurt my 1.3.9 users? Will it still work?
Thanks!
Mitch
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi - I don't know how to ask this question without it sounding a bit bitter, so please forgive me.
What is the logic used for replying to posts on this board? I've asked 2 questions in the last 2 months and gotten no answers, yet other questions get answered quickly.
I understand this is a free tool and I know that those supporting and developing it are giving their own free time to do so - but I would hope that fairness is in play as well and that people are willing to all chip in and help - otherwise why have this forum?
I've worked hard supporting other forums where I know the tools and the answers and know how tough it can be... but please don't let questions go unanswered here... how are people supposed to get the tools to work if honest questions go unanswered?
Thanks for your understanding.
Mitch
P.S. <begging> - anyone out there willing to help a newbie get the authorization for users working? I've tried and tried and read and read -- but i just don't seem to understand how to make version 1.3.9 or 1.3.10 work. :( email me off line at maunger at mac.com if you are - thanks </begging>
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can't speak for 'the group', just for myself. If I know an answer, I answer. If I don't, in general I don't answer. Unfortunately, there's a lot I don't know.
Reini knows most of the answers but is always doing tons of stuff.
I'd like to understand user authorization better as well. We need it to work smoothly and properly. I have not yet had time to look into it, and may not for months.
Almost certainly we are going to wait for the 1.3.11 release, as I think there were a number of changes to user prefs. (Am I wrong?)
You might also try the phpwiki-talk email list. I have this forum email me so it comes to the same folder, but perhaps the email list is read by more folks.
Perhaps you can consider just trying more stuff (make a copy of the DB, copy of dir, fiddle config to point to new DB, apply change, click around). I know that's not entirely satisfying (what did you miss?), but I wouldn't know how to do any better.
I don't know what more to say. I'd like to help if I know something.
Dan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I never even looked in the sourceforge 'list' page - so I didn't know there was a -talk email list so that will help. I wish i'd seen that sooner - thanks for that tip.
I'm new to PHP - i'm a coldfusion developer at work and have had classes in JSP but never touched PHP - so getting thru the code is a bit harder for me. I'm also just a hacker with mySQL so the tought of 'just trying it' bugs me a bit - especially when there are already users using my 1.3.9 system - guess I'll have to figure out how to do a new copy with a new database name etc.
I did download the 1.3.10 copy as of monday morning and so I'll keep working with latest copies and I've read the 1.3.11 plans... and maybe reading back in the phpwiki-talk archives will help a bit more with the authorization. I've got to get that to work somehow as I really need my wiki protected.
Thanks for taking the time to help
Mitch
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you need your wiki protected in a crude fashion, you might be able to do what I do: set up a single Apache user/pw to hand out to everybody. After they log in
> ALTER TABLE page CHANGE id id INT NOT NULL AUTO_INCREMENT;
>Will doing this mySQL change hurt my 1.3.9 users? Will >it still work?
That's a hard question. Why don't you just try it?
There's an optimization for mysql for ADODB which requires AUTO_INCREMENT so it will not work without.
adding AUTO_INCREMENT doesn't hurt.
But using the latest code without this sql upgrade will hurt.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I guess I will just have to bite the bullet and try to install to a different database within mySQL as i'm afraid to just 'try it' with 'production' users... can't be messing up the current installation.
I'm very new to mySQL and so I'm not familar with making that kind of change and without understanding the ramifications I'm not apt to just wing it.
Appreciate the answer
Mitch
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Again, thanks for this great tool!
I'm on 1.3.9 now and am looking at the 1.3.10 install - downloaded the latest copy this morning - and am reading the UPGRADE document... it has the comment about
mysql:
ALTER TABLE page CHANGE id id INT NOT NULL AUTO_INCREMENT;
I'm using mySQL and want to do the upgrade but I'm also wanting to make sure that this won't hurt my 1.3.9 users as I'd like to leave them running that version until I'm sure I'm ready to implement the 1.3.10 version...
Will doing this mySQL change hurt my 1.3.9 users? Will it still work?
Thanks!
Mitch
Hi - I don't know how to ask this question without it sounding a bit bitter, so please forgive me.
What is the logic used for replying to posts on this board? I've asked 2 questions in the last 2 months and gotten no answers, yet other questions get answered quickly.
I understand this is a free tool and I know that those supporting and developing it are giving their own free time to do so - but I would hope that fairness is in play as well and that people are willing to all chip in and help - otherwise why have this forum?
I've worked hard supporting other forums where I know the tools and the answers and know how tough it can be... but please don't let questions go unanswered here... how are people supposed to get the tools to work if honest questions go unanswered?
Thanks for your understanding.
Mitch
P.S. <begging> - anyone out there willing to help a newbie get the authorization for users working? I've tried and tried and read and read -- but i just don't seem to understand how to make version 1.3.9 or 1.3.10 work. :( email me off line at maunger at mac.com if you are - thanks </begging>
Mitch,
I can't speak for 'the group', just for myself. If I know an answer, I answer. If I don't, in general I don't answer. Unfortunately, there's a lot I don't know.
Reini knows most of the answers but is always doing tons of stuff.
I'd like to understand user authorization better as well. We need it to work smoothly and properly. I have not yet had time to look into it, and may not for months.
Almost certainly we are going to wait for the 1.3.11 release, as I think there were a number of changes to user prefs. (Am I wrong?)
You might also try the phpwiki-talk email list. I have this forum email me so it comes to the same folder, but perhaps the email list is read by more folks.
Perhaps you can consider just trying more stuff (make a copy of the DB, copy of dir, fiddle config to point to new DB, apply change, click around). I know that's not entirely satisfying (what did you miss?), but I wouldn't know how to do any better.
I don't know what more to say. I'd like to help if I know something.
Dan
Dan - well thanks!
I never even looked in the sourceforge 'list' page - so I didn't know there was a -talk email list so that will help. I wish i'd seen that sooner - thanks for that tip.
I'm new to PHP - i'm a coldfusion developer at work and have had classes in JSP but never touched PHP - so getting thru the code is a bit harder for me. I'm also just a hacker with mySQL so the tought of 'just trying it' bugs me a bit - especially when there are already users using my 1.3.9 system - guess I'll have to figure out how to do a new copy with a new database name etc.
I did download the 1.3.10 copy as of monday morning and so I'll keep working with latest copies and I've read the 1.3.11 plans... and maybe reading back in the phpwiki-talk archives will help a bit more with the authorization. I've got to get that to work somehow as I really need my wiki protected.
Thanks for taking the time to help
Mitch
If you need your wiki protected in a crude fashion, you might be able to do what I do: set up a single Apache user/pw to hand out to everybody. After they log in
I added the following to my phpwiki/.htaccess:
# Restrict access
AuthUserFile <full-path-here..>/phpwiki/.htpasswd
AuthType Basic
AuthGroupFile /dev/null
AuthName "Wiki Authorization"
Then I used Apache's htpasswd to generate the .htpasswd file I referenced.
I also had to change Apache's config file to "AllowOverride All" in a few spots, so it would take direction from phpwiki/.htaccess.
Dan
> ALTER TABLE page CHANGE id id INT NOT NULL AUTO_INCREMENT;
>Will doing this mySQL change hurt my 1.3.9 users? Will >it still work?
That's a hard question. Why don't you just try it?
There's an optimization for mysql for ADODB which requires AUTO_INCREMENT so it will not work without.
adding AUTO_INCREMENT doesn't hurt.
But using the latest code without this sql upgrade will hurt.
Thanks Reini
I guess I will just have to bite the bullet and try to install to a different database within mySQL as i'm afraid to just 'try it' with 'production' users... can't be messing up the current installation.
I'm very new to mySQL and so I'm not familar with making that kind of change and without understanding the ramifications I'm not apt to just wing it.
Appreciate the answer
Mitch