This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
181
Features / Re: New revs - Public comments
« on January 23rd, 2014, 03:19 AM »
"If I do one at a time I'll be done in 10 years"
:lol: Only understood this once I looked at the change in github :)
"is there an easy was to do this (update my installation with the latest rev.s) as I am on hostel WiFi so downloading a Zip and uploading its contents is unfair."
I've found that if I click on Commits it gives a list of commits, and clicking on each of these gives a list of changed files. And so I can download the latest zip and overwrite these files only :) (And I assume I have to clear the cache too.)
:lol: Only understood this once I looked at the change in github :)
"is there an easy was to do this (update my installation with the latest rev.s) as I am on hostel WiFi so downloading a Zip and uploading its contents is unfair."
I've found that if I click on Commits it gives a list of commits, and clicking on each of these gives a list of changed files. And so I can download the latest zip and overwrite these files only :) (And I assume I have to clear the cache too.)
182
Importing into Wedge / Database permissions
« on January 23rd, 2014, 02:29 AM »
So yes the absolute path works fine and I amended the opening post.
If the wedge database user does not have permission to the smf database then the following message is given:
Sorry, the database connection information used in the specified installation of Wedge cannot access the installation of %1. This may either mean that the installation doesn't exist, or that the MySQL account used does not have permissions to access it.
The error MySQL gave was: 'SELECT command denied to user 'wedgeuser'@'localhost' for table 'smf_members'
Obviously the importer works if the SELECT premission is given to the wedge user on the smf database.
If the wedge database user does not have permission to the smf database then the following message is given:
Sorry, the database connection information used in the specified installation of Wedge cannot access the installation of %1. This may either mean that the installation doesn't exist, or that the MySQL account used does not have permissions to access it.
The error MySQL gave was: 'SELECT command denied to user 'wedgeuser'@'localhost' for table 'smf_members'
Obviously the importer works if the SELECT premission is given to the wedge user on the smf database.
183
Importing into Wedge / Re: Importer tool
« on January 22nd, 2014, 01:01 PM »
I'll have another look at the path later :)
184
Importing into Wedge / Importer tool
« on January 22nd, 2014, 03:38 AM »
https://github.com/Wedge/importer
I have just used it and worked on my SMF 2 installation. However there was a bit of guesswork involved so to help others here's what I had to do.
1. the 'path to smf2' must be the relative address. So if wedge is in a subfolder off of your smf install then you need to input ../ (dot dot slash). For me SMF is in public_html and wedge is another folder off the root, and I access wedge using a subdomain. So I had to put ../public_html - the dot dot slash says "take me to the folder above this one." Absolute address works fine :)
2. The importer asks for the wedge database password but it then gave me an error as it wasn't able to read the SMF database. So the other thing I had to do was to give the wedge database user permission to the SMF database.
The above is not intended for techie people who are probably grinding their teeth at such language!
Anyway it worked well and everything seems to have been imported - even an unread message I received today :)
I have just used it and worked on my SMF 2 installation. However there was a bit of guesswork involved so to help others here's what I had to do.
2. The importer asks for the wedge database password but it then gave me an error as it wasn't able to read the SMF database. So the other thing I had to do was to give the wedge database user permission to the SMF database.
The above is not intended for techie people who are probably grinding their teeth at such language!
Anyway it worked well and everything seems to have been imported - even an unread message I received today :)
185
The Pub / Re: Wedge repo -- installation feedback
« on January 22nd, 2014, 01:25 AM »
Fair enough to all that; like I say I have it running on the web so I can use that :)
186
The Pub / Re: Wedge repo -- installation feedback
« on January 22nd, 2014, 12:23 AM »@Farjo, are you using Xamp, WampServer or something else?
Does that answer the question? If not I can follow instructions to find out more. And is it important given that it works on my web space?
187
The Pub / Re: Wedge repo -- installation feedback
« on January 21st, 2014, 11:56 PM »
I tried it again on my localhost and go the same message. However it works on my web space.
So the files are good, it's just my local zend that's got the issue. I don't know what info. you'd need (or probably where to find it). It's the free version, I installed it in July 2013 and have never upgraded it as I cannot work out how. The only app is phpMyAdmin 3.
So the files are good, it's just my local zend that's got the issue. I don't know what info. you'd need (or probably where to find it). It's the free version, I installed it in July 2013 and have never upgraded it as I cannot work out how. The only app is phpMyAdmin 3.
188
The Pub / Re: Wedge repo -- installation feedback
« on January 21st, 2014, 10:11 PM »
On my localost I get this message:
Your settings have now been saved and the database has been populated with all the data required to get your forum up and running. Summary of population:
Created 92 tables.
Inserted 800 rows.
Some of the queries were not executed properly. This could be caused by an unsupported (development or old) version of your database software.
Technical information about the queries:
Line #626: Field 'offlimits_msg' doesn't have a default value
Line #1735: Field 'data' doesn't have a default value
Click "Continue" to progress to the admin account creation page.
I am using:
Software: MySQL
Software version: 5.5.23 - MySQL Community Server (GPL)
Protocol version: 10
User: root@localhost
Server charset: UTF-8 Unicode (utf8)
Your settings have now been saved and the database has been populated with all the data required to get your forum up and running. Summary of population:
Created 92 tables.
Inserted 800 rows.
Some of the queries were not executed properly. This could be caused by an unsupported (development or old) version of your database software.
Technical information about the queries:
Line #626: Field 'offlimits_msg' doesn't have a default value
Line #1735: Field 'data' doesn't have a default value
Click "Continue" to progress to the admin account creation page.
I am using:
Software: MySQL
Software version: 5.5.23 - MySQL Community Server (GPL)
Protocol version: 10
User: root@localhost
Server charset: UTF-8 Unicode (utf8)
189
Features / Re: New revs - Public comments
« on January 21st, 2014, 09:06 PM »
Quote, from New Revs thread: Should I keep posting new revs here, when you can now just access the rev log here..?
https://github.com/Wedge/wedge/commits/
Is there a way to receive notifications of new revs? Personally I like reading them; even though I understand very little it does give an indication of areas that are being changed / added.
Another quote: Apparently, MySQL doesn't like being asked the unsigned keyword on bit fields. It should have been smart enough to ignore them, but whatever... (install.sql)
While I'm at it, minor regex simplifications. (install.php)
So one assumes that one can download those two files only and have the latest version of Wedge? (ie along with the zip I downloaded this morning[1].) And if so is there an easy was to do this as I am on hostel WiFi so downloading a Zip and uploading its contents is unfair.
https://github.com/Wedge/wedge/commits/
Is there a way to receive notifications of new revs? Personally I like reading them; even though I understand very little it does give an indication of areas that are being changed / added.
Another quote: Apparently, MySQL doesn't like being asked the unsigned keyword on bit fields. It should have been smart enough to ignore them, but whatever... (install.sql)
While I'm at it, minor regex simplifications. (install.php)
So one assumes that one can download those two files only and have the latest version of Wedge? (ie along with the zip I downloaded this morning[1].) And if so is there an easy was to do this as I am on hostel WiFi so downloading a Zip and uploading its contents is unfair.
| 1. | this afternoon Paris time |
190
The Pub / Re: Repository name poll! Yayer!!
« on January 21st, 2014, 03:55 PM »
Congratulations :)
191
The Pub / Re: Repository name poll! Yayer!!
« on January 20th, 2014, 10:20 PM »
Are you in danger of obsessing on this because you are nervous about releasing and subconsciously you are using this pontification to force a delay?
192
The Pub / Re: Last minute frights
« on January 20th, 2014, 01:16 PM »
Of those 5 either core or sys, but not root.
193
The Pub / Re: Last minute frights
« on January 20th, 2014, 03:27 AM »
But yes, I imagine it's like the night before a big important job interview - doing the last minute prep, suddenly noticing all the things you're not quite sure of and concentrating on those instead of all the things that you will shine at.
194
The Pub / Re: Last minute frights
« on January 20th, 2014, 03:25 AM »
It's a public release but it's not the actual actual release is it?? So you could give it the "don't use this on live" line which gives you plenty of time to change the bits (and bobs). Then so what if there's an update script to be run - it was just a test version.
(So is it an Alpha, Beta or RC?)
(So is it an Alpha, Beta or RC?)
195
The Pub / Re: Repository name poll! Yayer!!
« on January 18th, 2014, 05:18 PM »
'Open' - because the folder contains files that are open (I assume).
And if you release Monday 0030 it'll be the 20th where you are but still Sunday everywhere west.
And if you release Monday 0030 it'll be the 20th where you are but still Sunday everywhere west.