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
1966
The Pub / Re: Repository name poll! Yayer!!
« on January 16th, 2014, 08:04 PM »
Well, not really, unless you have it as a local remote, in which case you'll just need to update it. (git remote remove and git remove add or something, or simply TortoiseGit > Settings > Git > Remote, change casing, save.)
(I'm leaning towards Wedge/wedge currently, but... Whatever? I won't push today anyway. Too risky with the installer problems.)
(I'm leaning towards Wedge/wedge currently, but... Whatever? I won't push today anyway. Too risky with the installer problems.)
1967
Archived fixes / Re: Error during install
« on January 16th, 2014, 08:03 PM »
Ouch...
I don't even remember what step=3 is. What is the page before that one...?
(Reminds me that I need to fix step numbers in the URL. It starts with 0, then skips to 2 or 3, funny one...)
Can you test the newest push? Perhaps it'll fix it, although I doubt it... Both versions of the installer work perfectly for me. Damn you, white screens...!!!
I don't even remember what step=3 is. What is the page before that one...?
(Reminds me that I need to fix step numbers in the URL. It starts with 0, then skips to 2 or 3, funny one...)
Can you test the newest push? Perhaps it'll fix it, although I doubt it... Both versions of the installer work perfectly for me. Damn you, white screens...!!!
1968
Features / Re: New revs
« on January 16th, 2014, 08:01 PM »
[master 919e92f]
1 file changed, 33 insertions(+), 33 deletions(-)
Improved installer script by making sure that source caching is disabled. Known issue: user isn't auto-logged in after install. Honestly, I don't know why, so it'll remain there until I'm less tired, or someone fixes it for me. (That'll probably come down to the latter, because I can't really bother. Much.) (install.php)
1 file changed, 33 insertions(+), 33 deletions(-)
Improved installer script by making sure that source caching is disabled. Known issue: user isn't auto-logged in after install. Honestly, I don't know why, so it'll remain there until I'm less tired, or someone fixes it for me. (That'll probably come down to the latter, because I can't really bother. Much.) (install.php)
1969
Archived fixes / Re: Error during install
« on January 16th, 2014, 07:45 PM »
I've been on this since this morning, but was forced to a stop because I was a bit feverish. Tried to go to sleep, to no avail. Took an aspirin, watched a couple of Brooklyn 9-9, and I feel better now.
Anyway... I've fixed it, hopefully.
This installer is very complicated. I'm working on a slightly more solid version. Just a tad.
Please try this one, or wait a few minutes and try the newer one, thanks!
Anyway... I've fixed it, hopefully.
This installer is very complicated. I'm working on a slightly more solid version. Just a tad.
Please try this one, or wait a few minutes and try the newer one, thanks!
1970
Features / Re: New revs
« on January 16th, 2014, 07:42 PM »
[master cebde06]
4 files changed, 33 insertions(+), 30 deletions(-), 1.33 KiB
! Fixed installer. A lot of things were broken due to the theme removal process. I'm not sure it'll work perfectly everywhere, but it does for me. (install.php, Subs-PrettyUrls.php)
! Fixed incorrect margin on homepage top. (index.css)
* I thought I'd updated the homepage to be set to Home by default... Well, nope. So, I'm doing that now. I don't even know if I want to keep Welcome, at this point. (install.sql)
4 files changed, 33 insertions(+), 30 deletions(-), 1.33 KiB
! Fixed installer. A lot of things were broken due to the theme removal process. I'm not sure it'll work perfectly everywhere, but it does for me. (install.php, Subs-PrettyUrls.php)
! Fixed incorrect margin on homepage top. (index.css)
* I thought I'd updated the homepage to be set to Home by default... Well, nope. So, I'm doing that now. I don't even know if I want to keep Welcome, at this point. (install.sql)
1971
Features / Re: New revs
« on January 16th, 2014, 06:39 PM »
Got a bit behind, posting all of these revs at once, because I can...
a26b559 +1 -1 line
* ! Typo in announcement code was making this code not work. Doesn't matter much, as the feature needs a rewrite anyway, ahem... (Admin.php)
d094759d8c78c37b04fd9b09b54ba7a1728f2d64 +5 -5 lines
* ! Fixed an old missing language string. (Profile.template.php)
7e1134cd70b733a65fdb909934cacf89ffef791c +1 -1 line
* ! Fixed wrong JS filenames since the recent rewrite. The bug wasn't obvious, as the filename was still valid and JS still worked. (Subs-Cache.php)
b61078b2b4cbbe65ba09dc25456aef0e9199cba3 +1 -1 line
* ! Wess was using the user's preferred skin file, regardless of overrides. (Subs-Cache.php)
! Default skin was always Weaving. Oops. Okay, that was in the same line... (Subs-Cache.php)
[master 236f70c]
2 files changed, 52 insertions(+), 79 deletions(-).
+ Language caching no longer requires any particular language to have a matching file. Just one of the folders (English, default forum language and user language) needs to have it. If not found, then it's an error as usual. (Load.php)
! Custom language files were always being searched for, if not found. Wedge will now properly cache a non-existent custom file, and if you ever add one, then just flush the language cache. (Load.php)
! Wess will no longer leave $txt variables in if it can't find a matching language string. It'll just replace them with an 'Error' string, which is way, way better than the script refusing to execute, innit..? (Subs-Cache.php)
- Removed integrate_theme_include feature. Never used in Wedge. If a plugin needs this, there's a hook just below it. If a skin needs it, there's an include feature in skins, and if you really want PHP includes, I can look into it. (Load.php)
a26b559 +1 -1 line
* ! Typo in announcement code was making this code not work. Doesn't matter much, as the feature needs a rewrite anyway, ahem... (Admin.php)
d094759d8c78c37b04fd9b09b54ba7a1728f2d64 +5 -5 lines
* ! Fixed an old missing language string. (Profile.template.php)
7e1134cd70b733a65fdb909934cacf89ffef791c +1 -1 line
* ! Fixed wrong JS filenames since the recent rewrite. The bug wasn't obvious, as the filename was still valid and JS still worked. (Subs-Cache.php)
b61078b2b4cbbe65ba09dc25456aef0e9199cba3 +1 -1 line
* ! Wess was using the user's preferred skin file, regardless of overrides. (Subs-Cache.php)
! Default skin was always Weaving. Oops. Okay, that was in the same line... (Subs-Cache.php)
[master 236f70c]
2 files changed, 52 insertions(+), 79 deletions(-).
+ Language caching no longer requires any particular language to have a matching file. Just one of the folders (English, default forum language and user language) needs to have it. If not found, then it's an error as usual. (Load.php)
! Custom language files were always being searched for, if not found. Wedge will now properly cache a non-existent custom file, and if you ever add one, then just flush the language cache. (Load.php)
! Wess will no longer leave $txt variables in if it can't find a matching language string. It'll just replace them with an 'Error' string, which is way, way better than the script refusing to execute, innit..? (Subs-Cache.php)
- Removed integrate_theme_include feature. Never used in Wedge. If a plugin needs this, there's a hook just below it. If a skin needs it, there's an include feature in skins, and if you really want PHP includes, I can look into it. (Load.php)
1972
The Pub / Re: Repository name poll! Yayer!!
« on January 16th, 2014, 06:12 PM »
Actually I remembered that since only I have push rights to that account, no one is likely to have already added it as a remote... ;)
I'll keep watching the poll until I've committed all my bug fixes and am ready to push.
Tomorrow should be good.
I caught a cold this morning so it made things slower...
I'll keep watching the poll until I've committed all my bug fixes and am ready to push.
Tomorrow should be good.
I caught a cold this morning so it made things slower...
1973
The Pub / Re: Repository name poll! Yayer!!
« on January 16th, 2014, 04:01 PM »
wedge/wedge is winning; does that mean none of you cloned/forked the other repos in the Wedge account..? Because that *will* break any communication with them unless you take action... :^^;:
1974
The Pub / Re: Repository name poll! Yayer!!
« on January 16th, 2014, 01:13 PM »
NaoGilles/Wedge is a dead repo; because I rebased the original repo multiple times, I couldn't have pushed it to NaoGilles without breaking repos for everyone else. So, I pushed it to Wedge/Wedge so you can safely get my latest updates, as long as you're not pulling into the same repo, of course. (Or cleaning up, and force pulling, or something. I don't know what's available here.)
1975
The Pub / Re: Repository name poll! Yayer!!
« on January 16th, 2014, 01:05 PM »
I don't know what you mean.
If you're talking about BitBucket's Wedge repo, it's still private. It'll be a mirror for the github repo. I don't think I'll use it for starters, but if I'm bored with Github, I'll fall back to that one.
If you're talking about BitBucket's Wedge repo, it's still private. It'll be a mirror for the github repo. I don't think I'll use it for starters, but if I'm bored with Github, I'll fall back to that one.
1976
The Pub / Re: Repository name poll! Yayer!!
« on January 16th, 2014, 12:22 PM »
The poll is in favor of wedge/wedge, so I was going to go for that, but then I stumbled upon a small issue...
Yes, Github doesn't care about capitalization in your account and repo names. You can choose whatever you want.
However, git, itself, cares about it.
So, when I push my Wedge/languages repo to wedge/languages, I get an error saying Wedge/languages.git doesn't exist.
Oh, yeah.
Then again, it's not like the Wedge account has many 'followers' for now. So I could easily get away with forcing everyone to update their remotes. Hmm...
What do you think, guys..?
Yes, Github doesn't care about capitalization in your account and repo names. You can choose whatever you want.
However, git, itself, cares about it.
So, when I push my Wedge/languages repo to wedge/languages, I get an error saying Wedge/languages.git doesn't exist.
Oh, yeah.
Then again, it's not like the Wedge account has many 'followers' for now. So I could easily get away with forcing everyone to update their remotes. Hmm...
Posted: January 16th, 2014, 12:19 PM
What do you think, guys..?
1977
Plugins / Re: Calendar Plugin
« on January 16th, 2014, 11:19 AM »
So many things left to fix... ;)
I just need to determine when it's okay to release, even with bugs.
I just need to determine when it's okay to release, even with bugs.
1978
Plugins / Re: Calendar Plugin
« on January 16th, 2014, 10:51 AM »
If you want :D
Personally, I'm working on fixing the installer.
Personally, I'm working on fixing the installer.
1979
Plugins / Re: Calendar Plugin
« on January 16th, 2014, 09:42 AM »
Dunno if it works, though. I've tried to update it but I don't use it so it might be horribly broken.
1980
The Pub / Re: git rebase is a joke...
« on January 15th, 2014, 11:36 PM »You should rebase them.
You enter the branch andCode: [Select] git rebase master
Wouldn't git attempt to first take the entire master history, then apply whatever it doesn't find in the master history on top of it? That is, the entire 'alternate' (obsolete) history of the other branch?
Not that it matters much, because I didn't have enough diffs to justify re-doing these branches, but maybe for the future, I don't know...