Show Posts
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.
Messages - Nao
1411
Archived fixes / Re: Pretty URL | Unable to Post
« on February 18th, 2014, 10:14 AM »
Meh.. I never use that kind of thing.
1413
Archived fixes / Re: Latest commit breaks private messages
« on February 18th, 2014, 07:16 AM »
Looks like your database wasn't upgraded at all...
It works perfectly for wedge.org and my local install.
What is the value of your $we_shot variable in Settings.php?
It works perfectly for wedge.org and my local install.
What is the value of your $we_shot variable in Settings.php?
1414
Archived fixes / Re: Pretty URL | Unable to Post
« on February 18th, 2014, 07:14 AM »
Well, I'll need FTP access and a forum account (admin if you can, otherwise a regular account if you remember to re-enable all filters).
I'm not giving up on PURLs, myself...
I'm not giving up on PURLs, myself...
1415
The Pub / Re: Upgrading... how?
« on February 18th, 2014, 07:11 AM »CSS classes, not DB columns :)Quote from txcas on February 18th, 2014, 03:31 AM Also, I don't see hey_not or hey_pm in the members table.
They're DB columns, not CSS classes... :^^;:
1416
The Pub / Re: Upgrading... how?
« on February 18th, 2014, 07:11 AM »Should the version number go up to 1.0 or will is stay at 0.1 after the upgrade runs? I copied over the latest commits, but my version is still at 0.1.
1417
The Pub / Re: Upgrading... how?
« on February 18th, 2014, 12:14 AM »
Still the same.
Update the files.
Go to your forum.
Everything's upgraded transparently. If you're redirected to index.php?upgraded, then it means an upgrade just took place in the background. (I'm pondering whether I should actually show a "Upgraded" message, because even a guest can launch the upgrade process... I'm considering allowing this only for admins, but it means starting the upgrade after I've got proof that you're the admin, and at this point it might be too late to upgrade the database tables.)
Update the files.
Go to your forum.
Everything's upgraded transparently. If you're redirected to index.php?upgraded, then it means an upgrade just took place in the background. (I'm pondering whether I should actually show a "Upgraded" message, because even a guest can launch the upgrade process... I'm considering allowing this only for admins, but it means starting the upgrade after I've got proof that you're the admin, and at this point it might be too late to upgrade the database tables.)
1418
Archived fixes / Re: Pretty URL | Unable to Post
« on February 17th, 2014, 11:56 PM »
Yes, actually you can remove everything after the topic number (the human-readable part), your URL will still work... That's because Wedge doesn't waste time looking up a topic name in the DB to match it with a topic ID. It's more practical, I think, even if topic IDs aren't too cool, but at least they indicate whether a topic is older than another, etc.
Regarding your problem... I'm thinking, maybe it's due to the fact that you're in a sub-folder..?
Have you tried on a root folder..?
Regarding your problem... I'm thinking, maybe it's due to the fact that you're in a sub-folder..?
Have you tried on a root folder..?
1419
Features / Re: New revs
« on February 17th, 2014, 11:46 PM »
[Commit revision d8f0e00]
Author: Nao
Date: Mon, 17 Feb 2014 23:46:04 +0100
Stats: 1 file changed; +1 (insertion), -1 (deletion)
Author: NaoDate: Mon, 17 Feb 2014 23:46:04 +0100
Stats: 1 file changed; +1 (insertion), -1 (deletion)
- Last-minute typo™. Is important enough to warrant a push. (Upgrade.php)
1420
Features / Re: New revs
« on February 17th, 2014, 11:32 PM »
[Commit revision 52e4686]
Author: Nao
Date: Mon, 17 Feb 2014 23:31:56 +0100
Stats: 10 files changed; +97 (insertions), -39 (deletions)
Author: NaoDate: Mon, 17 Feb 2014 23:31:56 +0100
Stats: 10 files changed; +97 (insertions), -39 (deletions)
- Added upgrade tool to Wedge. This will automatically upgrade your database and files to what's currently expected. I'm not exactly sure what to do if two users are simultaneously running the upgrade script, as I'm not versed into multi-tasking, but... Well, if you have a suggestion on the nicest way to prevent that... (index.php, Upgrade.php)
- Which also means that I can celebrate by upping Wedge's version number from 0.1 to... 1.0, alpha 1. I'm not saying it's usable in production. I'm just saying we're getting closer to that. (index.php, changelog.txt)
- Added hey_not and hey_pm variables; these flags are set if you have new notifications (or PMs) and you haven't opened the notification popups yet. Basically, they control the notification button colors (orange or gray). (Class-Notification.php, Notifications.php, PersonalMessage.php, Subs-Post.php, Upgrade.php, index.template.php, install.sql)
- Root, source and plugin folders are now checked for existence within index.php, like the rest, rather than the settings file. Settings should only hold settings. (index.php, OriginalFiles.php)
- Tweaked the Settings.php automatically generated at install time. (OriginalFiles.php)
- Note: you may want to edit your Settings.php file to remove the multiple file_exists tests after "Make sure the paths are correct"... Really, it'll save your server some time.
1422
Importing into Wedge / Re: Importing member fields into members.data?
« on February 17th, 2014, 06:23 PM »
Oh... Good, then! I'd seen this preparsecode thing, but couldn't make sense out of it. Looks like it's just what I needed, thanks!
I'll get to work now...
So, would this work..?
Code: [Select]
I just wrote that, of course, haven't tested anything. Hopefully, the importer will catch that $row['data'] assignment and replace the existing value..?
I'll get to work now...
Posted: February 17th, 2014, 06:18 PM
So, would this work..?
<preparsecode>
// We're going to import some of SMF's member settings into the serialized data array.
$data = array(
'message_labels' => $row['message_labels'],
'modset' => $row['mod_prefs'],
);
if (!empty($row['secret_question']))
$data['secret'] => array(
$row['secret_question'], $row['secret_answer']
);
$row['data'] = serialize($data);
</preparsecode>I just wrote that, of course, haven't tested anything. Hopefully, the importer will catch that $row['data'] assignment and replace the existing value..?
1423
Features / Re: New revs
« on February 17th, 2014, 04:23 PM »
[Commit revision d911448]
Author: Nao
Date: Mon, 17 Feb 2014 16:13:25 +0100
Stats: 1 file changed; +2 (insertions), -2 (deletions)
Author: NaoDate: Mon, 17 Feb 2014 16:13:25 +0100
Stats: 1 file changed; +2 (insertions), -2 (deletions)
- Fixed the JS toggler, which had been broken for guests for a year now. Apparently, nobody ever noticed... Oops :) (script.js)
1424
Importing into Wedge / Re: Importing member fields into members.data?
« on February 17th, 2014, 04:17 PM »
Okay, because waiting was unbearable, I went for (c) by myself...
I wrote a <code> script (which happens after <presql> and before <query>, just what I needed) that imports elements from the table and then moves them manually to data. I removed 'data' from the query section, of course.
I'll now be working on importing as many elements as possible, i.e. anything that's not used in an index or modified on the fly for other members...
There's just one thing I don't know... If I have 10.000 members or something, how exactly am I supposed to split this query..?!
Or do I just rely on the fact that most of the members won't use the features I'm moving to data anyway..? (And thus, I can just make a query that skips members who use neither secret_question, nor message_labels, not mod_prefs, etc...)
I really could use your help, @TE!
I wrote a <code> script (which happens after <presql> and before <query>, just what I needed) that imports elements from the table and then moves them manually to data. I removed 'data' from the query section, of course.
I'll now be working on importing as many elements as possible, i.e. anything that's not used in an index or modified on the fly for other members...
Posted: February 17th, 2014, 11:22 AM
There's just one thing I don't know... If I have 10.000 members or something, how exactly am I supposed to split this query..?!
Or do I just rely on the fact that most of the members won't use the features I'm moving to data anyway..? (And thus, I can just make a query that skips members who use neither secret_question, nor message_labels, not mod_prefs, etc...)
Posted: February 17th, 2014, 11:29 AM
I really could use your help, @TE!
1425
Archived fixes / Re: Pretty URL | Unable to Post
« on February 17th, 2014, 02:54 PM »
Did you try to disable action URLs? With the other filters enabled? Does it work?