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
1306
Importing into Wedge / Re: SMF 2 to Wedge importer errors
« on February 27th, 2014, 03:12 PM »
Actually Pandos is right, board settings allow you to choose a new URL, so you might want to 'simply' visit all of your board pages again, then simply hit Save to re-generate the pretty URL. It might work.
:edit: Ninja'd! :lol:
:edit: Ninja'd! :lol:
1307
Off-topic / Re: Basic help with GitHub please
« on February 27th, 2014, 02:45 PM »
A few tips...
- TortoiseGit menu: the entry is called Git Commit -> "master", dunno if it's the same for you. You can edit the list of available menu commands through TortoiseGit > Settings > first 2 entries in the list view. Personally, I like having "Git Commit", "Git Show log" and "Git Blame" entries outside of the TortoiseGit menu group, because they're the 3 entries I use the most. I also use "Push" a lot obviously, but I prefer not to have it easily accessible.
- TortoiseGit > Settings > Git > Remote is one of the most important git settings. It allows you to control your 'remotes'.
A 'remote' is simply a URL that points to a remote repository, usually at GitHub, but it can be on any server that supports git of course, or even on your own machine, using the file:// protocol, for instance.
The 'common' way of doing things is:
- Add a remote called 'origin' which points to your Farjo/languages. For instance, https://github.com/Farjo/languages.git (you can add "Farjo@" before "github.com", so you don't have to enter your name in addition to your password. Of course, I'd strongly recommend that you use a tool to automatize git credentials, you can set this up in TortoiseGit > Settings > Git > Credentials.)
- Add a remote called 'upstream' which points to my Wedge/languages repo. i.e., https://github.com/Wedge/languages.git (of course.)
Now, the process...
- Right-click your repo, Pull, choose to pull from "upstream".
- Make your modifications.
- Push to "origin". Go to GitHub, and make a pull request.
- Anytime before making changes to your repo, make SURE to Pull upstream, otherwise you may break something.
As a note, you can also set your repo's pull origin & push destination to default values, but you'll have to use the command line for that. And I think that these days, TortoiseGit automatically selects your last pull/push remote, so it shouldn't be a problem.
- TortoiseGit menu: the entry is called Git Commit -> "master", dunno if it's the same for you. You can edit the list of available menu commands through TortoiseGit > Settings > first 2 entries in the list view. Personally, I like having "Git Commit", "Git Show log" and "Git Blame" entries outside of the TortoiseGit menu group, because they're the 3 entries I use the most. I also use "Push" a lot obviously, but I prefer not to have it easily accessible.
- TortoiseGit > Settings > Git > Remote is one of the most important git settings. It allows you to control your 'remotes'.
A 'remote' is simply a URL that points to a remote repository, usually at GitHub, but it can be on any server that supports git of course, or even on your own machine, using the file:// protocol, for instance.
The 'common' way of doing things is:
- Add a remote called 'origin' which points to your Farjo/languages. For instance, https://github.com/Farjo/languages.git (you can add "Farjo@" before "github.com", so you don't have to enter your name in addition to your password. Of course, I'd strongly recommend that you use a tool to automatize git credentials, you can set this up in TortoiseGit > Settings > Git > Credentials.)
- Add a remote called 'upstream' which points to my Wedge/languages repo. i.e., https://github.com/Wedge/languages.git (of course.)
Now, the process...
- Right-click your repo, Pull, choose to pull from "upstream".
- Make your modifications.
- Push to "origin". Go to GitHub, and make a pull request.
- Anytime before making changes to your repo, make SURE to Pull upstream, otherwise you may break something.
As a note, you can also set your repo's pull origin & push destination to default values, but you'll have to use the command line for that. And I think that these days, TortoiseGit automatically selects your last pull/push remote, so it shouldn't be a problem.
1308
Importing into Wedge / Re: SMF 2 to Wedge importer errors
« on February 27th, 2014, 02:35 PM »
You may have to run phpMyAdmin, edit the wedge_boards table, and modify all 'pretty_url' fields manually to match your new URL.
This is something that is better done with an automatic script, I guess, but I won't start work on this until I have a complete list of URLs and paths I'd need to update on the fly.
Also, I'm still wondering whether it's "worth" keeping variables such as $jsdir and $cssdir and others, when there really isn't much of a reason to 'hide' these files from view to visitors.
This is something that is better done with an automatic script, I guess, but I won't start work on this until I have a complete list of URLs and paths I'd need to update on the fly.
Also, I'm still wondering whether it's "worth" keeping variables such as $jsdir and $cssdir and others, when there really isn't much of a reason to 'hide' these files from view to visitors.
1309
Importing into Wedge / Re: Importer tool
« on February 27th, 2014, 10:31 AM »
[Commit revision 19cd1ad]
Author: Nao (Signed-off)
Date: Thu, 27 Feb 2014 10:30:45 +0100
Stats: 3 files changed; +20 (insertions), -4 (deletions)
Date: Thu, 27 Feb 2014 10:30:45 +0100
Stats: 3 files changed; +20 (insertions), -4 (deletions)
- I hate SMF's default colors for admin and global moderator groups. It may work if it's only used on the group color. But Wedge also uses these colors to show usernames everywhere, and it's just plain AWFUL, so I'm adding some code which will hopefully work on the first try, to replace them with the default Wedge colors. (smf2_to_wedge.xml, smf2RC_to_wedge.xml)
- Commenazi. (import.php)
1310
Importing into Wedge / Re: SMF 2 to Wedge importer errors
« on February 27th, 2014, 10:21 AM »
John, what are you trying to say..?
txcas, avatars should have been imported. Are attachments okay?
Make sure you didn't forget any of these steps:
- Let's say SMF is in /forum/
- Install Wedge in /forum2/ (or a sub-folder, but it requires some more work later)
- Run the importer
- Make sure /forum2 is working fine.
- Now, rename the /forum folder to /forum3, and immediately rename /forum2 to /forum
- Go to /forum, admin area, go to the 'Path' page (first sub-menu in the admin menu!)
- Fix all paths.
- Go to avatar and attachment settings pages, and fix all paths.
- IIRC, you also have to go to the skin settings page, and fix paths.
I should be building a tool to automatize the fixing of ALL paths with the 'wrong' folder in their name, if the main folder was modified... Oh yeah, that would be swell.
At this point, Aeva Media items still aren't imported. You'll need to move /forum3/media files to /forum/media, and then manually import AeMe database tables into the new location... Well, that one is NOT fun. Unfortunately, because @TE doesn't seem to want to finish the importer tool to support AeMe files (and I'm still not familiar enough with it to deal with adding an import step myself), upgrading your forum at this point MAY mean you'll lose your existing AeMe data forever.
Also, looking at your site, I really need to do something about the header CSS... Obviously, the header at wedge.org is working well, and it's not so good elsewhere, because I have custom.css CSS I never bothered to commit, but I really need to do it at this point.
txcas, avatars should have been imported. Are attachments okay?
Make sure you didn't forget any of these steps:
- Let's say SMF is in /forum/
- Install Wedge in /forum2/ (or a sub-folder, but it requires some more work later)
- Run the importer
- Make sure /forum2 is working fine.
- Now, rename the /forum folder to /forum3, and immediately rename /forum2 to /forum
- Go to /forum, admin area, go to the 'Path' page (first sub-menu in the admin menu!)
- Fix all paths.
- Go to avatar and attachment settings pages, and fix all paths.
- IIRC, you also have to go to the skin settings page, and fix paths.
I should be building a tool to automatize the fixing of ALL paths with the 'wrong' folder in their name, if the main folder was modified... Oh yeah, that would be swell.
At this point, Aeva Media items still aren't imported. You'll need to move /forum3/media files to /forum/media, and then manually import AeMe database tables into the new location... Well, that one is NOT fun. Unfortunately, because @TE doesn't seem to want to finish the importer tool to support AeMe files (and I'm still not familiar enough with it to deal with adding an import step myself), upgrading your forum at this point MAY mean you'll lose your existing AeMe data forever.
Also, looking at your site, I really need to do something about the header CSS... Obviously, the header at wedge.org is working well, and it's not so good elsewhere, because I have custom.css CSS I never bothered to commit, but I really need to do it at this point.
1311
Features / Re: New revs
« on February 27th, 2014, 10:12 AM »
[Commit revision 7a91f08]
Author: Nao
Date: Thu, 27 Feb 2014 10:12:33 +0100
Stats: 2 files changed; +4 (insertions), -12 (deletions)
Date: Thu, 27 Feb 2014 10:12:33 +0100
Stats: 2 files changed; +4 (insertions), -12 (deletions)
- Arrrrrgh. Finally fixed the upgrader bug, and understood why I was unable to reproduce it. See, I called the upgrader after loadDatabase (so I could access the DB) and before loadSettings (so I could make fixes to settings before they're loaded), and SET NAMES 'utf8' was called by loadSettings, against all expectations. Thus, any database operations made from the upgrader weren't forced to UTF8, and this screwed up accented characters. Moved it to loadDatabase, where it should have been from the start! Oh my, you have no idea how relieved I am to be finally done with this. (Load.php)
- Reverted my fallback code, thanks to this fix. (Class-System.php)
1312
Importing into Wedge / Re: SMF 2 to Wedge importer errors
« on February 27th, 2014, 12:09 AM »
message_labels is a valid members table fields in SMF 2... I don't know why it wouldn't work.
@TE, what do you think..? Is the <preparsecode> block buggy..?
Off to bed, personally.
@TE, what do you think..? Is the <preparsecode> block buggy..?
Off to bed, personally.
1313
Features / Re: New revs
« on February 27th, 2014, 12:04 AM »
[Commit revision c0d39fe]
Author: Nao
Date: Thu, 27 Feb 2014 00:04:32 +0100
Stats: 1 file changed; +6 (insertions), -4 (deletions)
Date: Thu, 27 Feb 2014 00:04:32 +0100
Stats: 1 file changed; +6 (insertions), -4 (deletions)
- A more universal version of the Latest Posts block in the homepage. Also, it's now more responsive, like the Latest Thoughts block. (Home.template.php)
1314
Importing into Wedge / Re: SMF 2 to Wedge importer errors
« on February 26th, 2014, 11:57 PM »
Is this during the attachment import step..?
If yes, please test the new committed version.
If yes, please test the new committed version.
1315
Importing into Wedge / Re: Importer tool
« on February 26th, 2014, 11:57 PM »
[Commit revision bf6dbf2]
Author: Nao (Signed-off)
Date: Wed, 26 Feb 2014 23:57:15 +0100
Stats: 2 files changed; +2 (insertions), -2 (deletions)
Date: Wed, 26 Feb 2014 23:57:15 +0100
Stats: 2 files changed; +2 (insertions), -2 (deletions)
- Wrong position of a free_result call. (smf2RC_to_wedge.xml, smf2_to_wedge.xml)
1316
Features / Re: New revs
« on February 26th, 2014, 11:50 PM »
[Commit revision e1d820f]
Author: Nao
Date: Wed, 26 Feb 2014 23:50:35 +0100
Stats: 1 file changed; +34 (insertions), -33 (deletions)
Date: Wed, 26 Feb 2014 23:50:35 +0100
Stats: 1 file changed; +34 (insertions), -33 (deletions)
- Fixed a couple of bugs that screwed up the scroll position for very large select boxes (again: think timezone selector), in at least one specific situation: opening the dropdown below the select box, closing it, then scrolling up and reopening the dropdown above the select box (or the other way around.) This fix costs about 30 gzipped bytes, for something no one will ever notice, but when it comes to sbox, I'm a perfectionist. (sbox.js)
- Also fixed center positioning of currently selected select box item when reopening the select box in the same fashion. Costs another 10 bytes or so... (sbox.js)
1317
Archived fixes / Re: Date format is incorrect
« on February 26th, 2014, 10:56 PM »
In French, the date format doesn't really matter, because it's likely the 'Today at..' will be longer anyway, as it's "Aujourd'hui à...", which is quite long. Also, if Lorenzo posted the last message in a topic, it'll also make the first column longer, because of his very long username... :P
Anyway, yeah, that was the idea, trying to harmonize the topic list with the thought list. I'm not a big fan of the result, though, I may end up moving the user names elsewhere.
Anyway, yeah, that was the idea, trying to harmonize the topic list with the thought list. I'm not a big fan of the result, though, I may end up moving the user names elsewhere.
1318
Importing into Wedge / Re: SMF 2 to Wedge importer errors
« on February 26th, 2014, 10:54 PM »
I'm on it. Will commit fixes asap.
Committed. Keep me posted!
Posted: February 26th, 2014, 10:44 PM
Committed. Keep me posted!
1319
Importing into Wedge / Re: Importer tool
« on February 26th, 2014, 10:53 PM »
[Commit revision d65f1ff]
Author: Nao (Signed-off)
Date: Wed, 26 Feb 2014 22:53:38 +0100
Stats: 2 files changed; +28 (insertions), -9 (deletions)
Author: Nao (Signed-off)Date: Wed, 26 Feb 2014 22:53:38 +0100
Stats: 2 files changed; +28 (insertions), -9 (deletions)
- A couple of errors in the latest commit. Hopefully this should be enough to let txcas import... ;) (smf2_to_wedge.xml)
- Applied the same fix to the SMF 2 RC import code, while I'm at it... (smf2RC_to_wedge.xml)
1320
The Pub / Re: will there be a slideshow for zoomedia in the beta release?
« on February 26th, 2014, 10:09 PM »
There won't. Although I'm currently in a JavaScript focusing phase, I have no plans yo further work on zoomedia during that time. If I work on media stuff I'll instead focus on adding mediaelement.js support and write a playlist system for it so I can get rid of jwplayer.
Anyone is free to offer to work on Zoomedia though... the code is short and simple. Adding a slideshow wouldn't be hard but I'd like for it to be better integrated with AeMe, unlike highslide's.
Anyone is free to offer to work on Zoomedia though... the code is short and simple. Adding a slideshow wouldn't be hard but I'd like for it to be better integrated with AeMe, unlike highslide's.