As many of you already know, the original auto-linky widget is currently disabled. If you have a gold membership, locate any script that says “autolink.php” and replace “auto” with “easy” to use the easy-linky widget, which is not affected.
Thank you for your patience while we work out the performance issues and towards bringing back the original auto-linky widget.
Update: the original auto-linky can only be offered on the new server at the present time.
During this period of system overload condition, I feel it is of the utmost importance, while stabilizing the system, to provide the best possible service to those users with upgraded memberships.
I have therefore had to restrict standard memberships on a TEMPORARY basis. Rather than seeing links right in the post, you may need to click a link to see them and enter new links. I hope intend to remove this restriction as soon as possible.
Thank you for your continued patience and understanding!
You might have used “gadgets” to put the header script in your blog. If so, these instructions are for you.
1. Go to your Blogger dashboard and click the Layout tab.
2. If you have a gadget called “Mister Linky” that is probably it, but it might be a different one called “HTML/Javascript”
3. Click the Edit link of each gadget until you find something like this line — note, it might single or double quotes, and type “type” and “scr” parts might be reversed, the important thing is that it say “header.js” in it:
<script type=”text/javascript” src=”http://www.blenza.com/linkies/header.js”>
…and delete just that line.
5. Once you’ve found it, click the blue Remove button.
6. And that’s it! Thank you very much for helping with this!
1. Go to your WordPress admin page
2. Click on “Appearance” and on “Theme Editor” or “Editor”
3. In your list of files, locate “Header” or “header.php” and click it.
4. Look for something like this line near the top — note, it might single or double quotes, and type “type” and “scr” parts might be reversed, the important thing is that it say “header.js” in it:
<script type=”text/javascript” src=”http://www.blenza.com/linkies/header.js”>
…and delete just that line.
5. Click the “Save” or “Update File” button, whichever you have. If WordPress tells you that you can’t save the file, file a ticket and I’ll help you through it.
6. And that’s it! Thank you very much for helping with this!
1. Go to your Blogger dashboard
2. If you have a “Layout” tab, click it, then click “Edit HTML” and go to step #4
3. If you have a “Template” tab instead, click it and proceed to step #4
4. look for something like this line near the top — note, it might single or double quotes, and type “type” and “scr” parts might be reversed, the important thing is that it say “header.js” in it:
<script type=”text/javascript” src=”http://www.blenza.com/linkies/header.js”>
…and delete just that line.
5. Click orange “Save Template” or “Save Template Changes” button, whichever you have.
6. And that’s it! Thank you very much for helping with this!
Hi — I’ll give you a news update soon, but if I could ask everyone a HUGE favor — please please please would you REMOVE the header script from your template. It looks something like this line — note, it might single or double quotes, and type “type” and “scr” parts might be reversed, the important thing is that it say “header.js” in it:
<script type=”text/javascript” src=”http://www.blenza.com/linkies/header.js”></script>
Just take it right out of there. It’s causing this terrible system load and I’ve promised our hosting service that I’d ask users to remove this, and that’s when they started the server back up. I’m taking steps to make sure the widgets will all work without it.
So, if you’d please please please do that, we’d all be wicked grateful. Thanks! Note, instructions are available for:
OK, and here’s the update I promised. Our server has been behaving badly of late. I’m sure you’re well aware of that, and that’s not news. I’ve been working on ways to make things run more smoothly, but something came to light today that has been a big part of the problem that I was not aware of. See above — the header script. It causes all kinds of work on the server, even when you page isn’t displaying a widget! So I’ve had to rework a bunch of stuff to make sure the widgets will work without it, and that’s why I’m asking you all to remove that tag from your pages. It will make everything run much faster on the blenza server and also on your own page, too.
Back later, I’ve got a couple hundred help desk tickets I need to point back here. I’m sorry to have to respond with just a quick link, but I want to make sure everybody gets updated as soon as possible.
My apologies for the inconvenience of today’s downtime, and I thank you for your patience and understanding as I work to get this thing working smoothly.
A new link repository has been added to the system, which should deliver links much faster, and give us much better overall system performance. The system has always stored all incoming links in a database, and will continue to do so. However, we will also cache the links, so that the database doesn’t have to be queried each and every time someone loads a page. What this means is that after a link is left on your site, it might take up to a minute for that link to appear when someone else comes to your site. This fine-tuning of this system will take some time to get just right, so please bear with us during this transition.
Again, my apologies for the instability of the system over the past week or so. Part of this was because of a hardware issue that, once resolved, took some additional fixing on the part of technical support at our hosting service. But the overall performance should improve noticeably — now, and especially after the transition to caching has been completed, a few days from now.
Please follow Mister Linky on Twitter for (hopefully) timely updates, and report any issues at the Help Desk.
Our hosting service is working a hardware issue. I’ll let you know once they update me.
Note, for current status for this and other issues, you can follow @misterlinky on twitter.com.