To keep in synch with what is at github at the moment.
If something is broken... well, you know who you should blame! :P
Another bump with the most recent version in master. :D
Commit e0f0c81f82de7fa1f62461dbe51353b3d8b55336
PR #1668
Another one.
Commit 0c1f3922e80f56b585fb3bd702c79c87adceef76
PR #1712
Commit: 2a2e8f2666feda84f4af790cc5626f438d907dbc
PR #1725
Commit: 6e988f3e8cdd00791fbd6ae432b996d63364ab9f
PR #1728
Bumped to what should be RC2.
What do we do? Release? O:-)
I had to merge in the PR I had pending ... one item was code cosmetics, but the other prevented you from changing the search method on the site so had to be fixed :(
Bumped to post-RC2.
Commit: bc6156286f483cfd58a64ceacbc8ae223e5fd2d7
PR #1751
Party :D
Commit: 833c37e3fc26a4afaaf7987a8e64f3d9c6812948
PR #1772
Sorry, I was working on some non-working code while uploading and I forgot the forum was in maintenance mode... :-[
I was too concentrated trying to understand what was wrong... lol
Anyway, commit: da595e3813c1664cfff522e80d65f5c045b316ae
PR #1789
LOL ... I've never done that before O:-)
Updated to commit cfefc747da1fb86f01c796407a277e1a04d46760
Pull request #1761
That is already slightly after 1.0 and inside 1.0.1.
Woot ! ... Thanks !
Updated to commit 3c91ce3a6cead8ccfc16b02b1319fd7887ec0766
Pull request #1818
On the road for 1.0.1
Coolness !
The automatic word shortener rocks.
"Another small bum..."
Out of curiosity where did you see that? The text cutter can be set to hard or soft, meaning it cuts exactly at xx or if it tries to find an appropriate word boundary, there are needs for both cases.
I think that one is on the board index. lol
LOL well thats a bum mer
Updated to the latest 1.0.1 patch.
Commit cd786921abd32588d9d12f754678fd870f61a865
Pull request #1834
I guess this shouldn't look like this:
(http://i.imgur.com/PdAI4IF.png)
and what happened to ?action=who?
(http://i.imgur.com/0fCgTnn.png)
Just a mess while caching the css files.
Now looks fine.
As soon as the patch is ready.
What is missing?
At the moment there is another PR after the last time I updated the files, and there may be the linktree stuff (but I could live without it for the moment and postpone it to 1.0.2).
Originally I placed my bet on the 5th of October as release date (see github), it is still possible. :P
1.0.1 final is now running here too... O:-)
I just uploaded the current HEAD of patch_1-0-2:
commit: 769cf602ee7b3eadc65e9a176abfd44a5fc8f6c6
PR: #1885
At first I did a bit of a mess because I uploaded by mistake a "dirty" repository (the one I use for development that is full of files of addons and stuff, so I had to wipe out sources and themes and re-upload everything.
Actually I hope I re-uploaded everything, so if you see anything broken, it's my fault, feel free to report... :-[
Ah cool thing to do ... gets some more testing on 1.02 :D Want to get that out in December!
Another one!
commit 202242a07ed26e81a3976d7fc69b9f703043cd5e
Pull request #1891
Tomorrow I'll try to bring the site to 1.0.2... now it's a bit late.
Just did the 1.0.2 update, did not run update.php as I think that was done already. The site was almost at 1.0.2 I thnk, now it is.
In December I'm way too lazy apparently... LOL
Thanks Spuds! :D
Another update to the current patch 1.0.3 branch, after the merging of the PR 1954
Commit: 36b057a9368a982459dd0673edb74b4268eb321d
Plus a couple of tweaks not yet in the repo.
Bumpity.
commit: f2bf8886911b9eece85e8a9b3ea944fae37ad399
Pull request #1958
8)
Finally 1.0.3... :p
While I having the ftp open, I also uploaded some language packs, good for tests. O:-)
I was going to ask when, but today I saw you just update ;)
Yeah it was kind of at 1.0.2++ but not quite 1.0.3 :D ... Thanks Eman !
I think it was missing just a couple of undefined indexes (the error log was rather long LOL) fixed in the last patch.
First round of fixes for 1.0.4 applied! :)
Commit fe68db15201deb07222bb197bdbaf73589c4e3e0
Pull request #2055
Awesome !
Update to commit 60f189a4bd79a9b1e6cab7a0ce975590a29d3338
Merge pull request #2144 from Spuds/patch_1-0-5
Cool :D
/me is waiting the moment 1.1 will be on. O:-)
Me too! :)
Bumpity to :
commit 5427bd9db846e03a84dd0e11f3375c6b2ebd7242
Pull request #2174
Here is already updated to 1.0.5 :) I'm testing it already.
Another bump ... now up to commit a394196c70517d61cbab868939241759c21ebbc7 on branch 1.0.5
Great! :D
Hey it haz cutesy little house in the linktree. :D
ETA: Hmm. TBH cutesy little house not so good IMO. Problem is that it gives a very small target for teh clickies when you want to use the linktree to go back to the home page. It could really do with some extra padding on that anchor to make it more usable,
The problem is that since you're just using one of these nifty new icons fonts, there's no actual text. That means nothing for the CSS to grab to give the anchor the same line-height and horizontal paddings as the other linktree links.
Result is that the anchor collapses to the size of the icon itself, which is bugger all.
So yeah it's cute, but it's not very practical in its present format.
ETA again: Aha. So it's pulling in some weird CSS from some other classes. Probably from FA framework. Does FA stand for F**k All? :D
suppose one could wrap it with or #8239;
Should just be able to target it with CSS directly. Something like this should do it:
.linktree:first-child a {height: 2em; padding: 0 6px; }
Unless I'm missing something and FA is going to bork that somehow (haven't worked with FA yet so don't actually know).
its live
Yeah that sorts it, whatever you did. :)
And here we are with the is-to-be 1.0.6! :D
I think its our smallest update to date :D
Not so fast! I still have problems to solve with 1.0.5! :D
LOL ... did I hear 1.0.7 :P
This site has become very slow for me. I hope it's not the update. Pages take a few seconds longer to load now. Just a wait at the beginning. Two different networks.
Been real slow for me today as well .... don't believe its the update though, but have been getting >10s response times for some pages.
For example, this post was: Page created in 20.070 seconds with 22 queries.
Similar to what I'm seeing as well. I also suspect server issues more than the update but figured I should mention it.
I thought it was just my internet connection... O:-) :(
Nothing wrong at my end. Was loading as usual.
I experience the delays too.
Same with me. I have tested it since OP.
Now is fine for me: Page created in 0.094 seconds with 26 queries.
Seems fine for me as well ... must have been some network issue in the data center
Site's been okay for me, except one issue.
When click to mark all boards read, the top bar sticks at loading, until I close it, manually.
But, this does not happen all the time, just every now and then, so it could jut be server hiccups.
/me thinks it's about time to push live the 1.0.7 code
Tomorrow. :P
Done, update to:
commit 4e9a69f8213ba01c121bc11cdb1c6471d03acb75
Pull request #2412
When will 1.0.7 be available for download? Current zip show 1.0.6 and I am jonesing for the 1.0.7. :)
I hope about next week (given or taken few days). I'd say not later than the end of the month.
It's a sort of "unexpected" release since in theory we should be already running the 1.1 show, but being late and having spotted few things that need an adjustment, here we are.
Updated with the code that should be 1.0.7.
/me goes bed now.
If something breaks...
/me blames... Spuds. :P
Awesome ... well except for that blame me part :P
What do you think if I put 1.1 up here? O:-)
Your a mad man !! ... .of course we need to do that at some point nods that's how we got to really exercise 1.0 to find them buggies
Well, at least the upgrade seems to work, so it should be kind of safe... O:-)
Are the colors used for the icons here standard for 1.1? :o
Not sure what happend before but the attachment settings on this site seems to be broken, no clue what could have caused it.... at the moment only the quick reply works..
I'll fix the database entry when I'm home, likely in 6/7 hours.
fixed it by adding back the content of attachmentUploadDir.. upgrade.php bug ?
No... well, yes, but I already fixed the entry in the database just after the upgrade, so it was working properly (also because we attached a fair share of stuff recently). Instead now something changed and broke it again.
Unless someone changed some setting or did some maintenance, the only suspect I have is the auto-generation of directories, that is a bit odd because it should not kick in until the end of the month...