Click here to edit contents of this page.
Click here to toggle editing of individual sections of the page (if possible). Watch headings for an "edit" link when available.
Append content without editing the whole page source.
Check out how this page has evolved in the past.
If you want to discuss contents of this page - this is the easiest way to do it.
View and manage file attachments for this page.
A few useful tools to manage this Site.
See pages that link to and include this page.
Change the name (also URL address, possibly the category) of the page.
View wiki source for this page without editing.
View/set parent page (used for creating breadcrumbs and structured layout).
Notify administrators if there is objectionable content in this page.
Something does not work as expected? Find out what you can do.
General Wikidot.com documentation and help section.
Wikidot.com Terms of Service - what you can, what you should not etc.
Wikidot.com Privacy Policy.
All of my sites that I have checked so far are broken with the page-options-buttons missing. Yes I can use a keyboard shortcut to edit a page but my users won't know about that. Not currently happy about this at all, particularly as we were given no warning and I found out from one of my users at the same time the posts started appearing on the community forum.
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
I had set the #page-info to display:none. Taking that out and the buttons have re-appeared. But having to check all sites.
And why put the page options buttons inside page info anyway?
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
Ah, so there's another problem. The page options got launched into the page info; that's most certainly wrong.
Luckily, I have the old page structure on the archaic CSS Zone, so anything suspicious can be checked up there to see what changed.
Timothy Foster - @tfAuroratide
Auroratide.com - Go here if you're nerdy like me
Something is messed up, I'v checked inside layout template and #footer is obviously outside #content-wrap block, probably someone left unclosed html element somewhere, we will fix it.
Bartłomiej Bąkowski @ Wikidot Inc.
';.;' TeRq (Write PM)
Why would you guys do this? It really messed up the icon deposit!! My site is all over the place! Now whats going to happen to all my traffic???
CEO of Icon Deposit
Take a look at me via Twitter, Dribbble, and Google +
I don't think this was some kind of malicious attempt to break our sites. As TeRq said, they made a mistake and will fix it when they find it.
Community Admin
I understand it's definitely not a malicious attempt. There are just so much unnecessary security that if we were just able to edit the HTML of our wikis (not the <head>) This would have never had happened. And I'm not trying to sound like an a** here, but my site was ranked at 97,052 in the US this morning on alexa.com and now it's ranked over 100 thousand. Pretty sure it was because of this.
CEO of Icon Deposit
Take a look at me via Twitter, Dribbble, and Google +
I had to spend 2 hours tonight fixing broken sites so users could (if they wished to) edit them when I actually had pressing deadlines on other sites. And once it's fixed I will probably have to spend another 2 hours reverting the changes. Mistakes happen but something this critical is really annoying.
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
Seriously Rob I feel your pain so much.
Wait so they're not going to fix what happend?? I have to fix this myself?
CEO of Icon Deposit
Take a look at me via Twitter, Dribbble, and Google +
No, hopefully they will fix this. But it's embarrassing for them and real headache for us.
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
It's embarrassing for me right now. This is making my company look bad. I had a really nice website just hours ago, now it's so messed up, I can't figure out the problem and this is reeallllllllly pissing me off.
UPDATE: I just fixed the stupid annoying problems that went on with my site. The problem here was in the "extra-divs and extrac-divs" and the "footer".
CEO of Icon Deposit
Take a look at me via Twitter, Dribbble, and Google +
Bartłomiej Bąkowski, Wikidot Inc.
…. TeRq
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?
Everything should be fixed within an hour. I'm really, really sorry for all the inconveniences. Unfortunately, you will all have to make reverts to all changes made for fixing this awful and annoying problem.
Guys, as Squark said, all is back to normal now. And shit happens, especially when a few different things overlap.
First of all, there was a failure in our work process — if you want to know the details. We are using git for managing application code and it works great. Over the last few years we have worked out an efficient way of developing, testing and deploying new features that is as much bullet-proof as we think is sufficient.
We have two major branches in the git repository: master and test. Whenever we start working on something new, we create "feature branches", which originate from master. When they are ready to test, we merge them into the test branch. If code needs fixing, the fix is done in the feature branch and merged into test again. And so on. When the feature is ready, it is being merged into master and deployed to our server.
Now, we started working on an improvement related to sending emails a week ago. But (as a result of human mistake) the branch originated from test instead of master! At that time the test branch had at least 2 incomplete features (that were fixed in the next few days). As we worked on emails, we were merging them into test, and it all worked fine — the process converged into a zero-error state.
The problem was when we merged the branch into master. The non-finished features that were present in test at the time the branch was created got to our production servers. Although we fixed some of them quickly, some went unnoticed.
Another thing, the errors (including the most appearing one, the lack of </div> in page options) were not detected by our automated test.
And it was the end of the day, when we gladly went home to get some rest.
It was today morning that we reset all our git repositories and refactored the working tree so that all changes are where they should be.
I am sorry for the mistake we made and that we did not fix it in time. Sh*t happens, but every such failure is a tough lesson for us. It is difficult to say which situation is more stressing: "my site did not work" or "we failed people and their sites did not work", but except a few mistakes we really do our best to keep your stuff up and running.
Michał Frąckowiak @ Wikidot Inc.
Visit my blog at michalf.me
And for that I (and hopefully the rest of the community) am especially grateful. Sure, mistakes happen. We could point the finger and get angry and move our sites elsewhere, but would it really be worth it? So some sites didn't quite look right for half a day. There are bigger things in the world to worry about. Plus, it's nearly Christmas. Where's the festive cheer? :)
BMC Creative | RoaringApps | @brycecammo