Absolutely nothing happened in Sector 83 by 9 by 12 today. I repeat, nothing happened in Sector 83 by 9 by 12.
Sunday, February 05
Design Refresh
I'm doing a new design for the next version of Minx, based on the 960.gs / Skeleton / Bootstrap CSS layout libraries.*
The rounded corners are likely to go at this stage; form design will improve, and blogs will resize (at least in theory) to fit your device, but in discrete steps rather than one pixel at a time.
The idea is that you'll choose a 12- or 16-column layout, and then assign a certain number of columns to each element on the page, so you might choose 12 columns, and allocate 8 to the content and 4 to the sidebar. But you could also have a headlines area (between the banner and the content) with three items each four columns wide.
The new base widths will be 700 pixels (for smaller devices like tablets and phones), 940 pixels (for older PCs and notebooks), and 1180 pixels (for larger screens). All of those work out evenly whether you choose a 12- or 16-column grid.
There will be a pair of new, interactive menu bars above and below your banner image, the top one for the mee.nu system as a whole, the bottom one for your site. The current ads (which I haven't sold any of yet anyway) will shrink down to fit in the top menu bar, rather than sitting above it, and will expand out on mouseover. I think that's the best compromise to make them as unobtrusive as possible while still giving advertisers a useful amount of space.
Sample Images
Update: Damn arithmetic! One problem with the above layout is that to fit ads neatly in the sidebar you'd want it to be 240 pixels wide - the same as the ad itself. But the maths just doesn't work out.
With a 940-pixel standard layout, you have 12 columns each 60 pixels wide, and 11 margins in between each 20 pixels wide. 12 x 60 + 11 x 20 = 940.
With 16 columns, it's 16 x 40 + 15 x 20 = 940.
This works because we're ignoring the rightmost 20-pixel margin - if we included that, the widths would be 720, 960, and 1200 pixels - all multiples of 240, with lots and lots of useful factors.
So if you have a 3 column sidebar in a 12-column layout, that's 3 x 60 + 2 x 20 = 220px. 4 columns in 16-col layout is 4 x 40 + 3 x 20 = 220px. Either way, too narrow for the ad. 4 columns in 12-col layout is 4 x 60 + 3 x 20 = 300px; 5 columns in 16-col layout is 5 x 40 + 3 x 20 = 280px, which leaves a fair chunk of space over.
I'm not sure how bad that will be in a live design, so I'm not going to tear up the fundamental principles of mathematics just yet. And you could force the sidebar into a 240-pixel layout within a 280/300 pixel division if need be, with a larger than normal gap between the sidebar and the main content.
Real-world testing is indicated here.
* Most likely Bootstrap; I had some issues with version 1.4, but the newly released 2.0 cleans up most of the things I didn't like and adds even more features.
Okay, I've lined up reasonably-priced providers in the following locations:
Phoenix (2)
Dallas (2)
Atlanta
New Jersey
Chicago
Los Angeles
Fremont
I'm not sure about the company operating the Chicago and Fremont hosting - they seem to have happy customers, but they're small and operate out of Malaysia. Mind you, I'm even smaller and operate out of my living room...
One of the providers in Phoenix - I/O Flood - is also a tiny company, but they clearly know what they are doing (very active online) and their pricing is great. The other two providers have been in business for years and I've had servers with both of them previously, but they're the most expensive. (But still significantly cheaper than what I'm paying now.)
Fremont, Dallas, and New Jersey would make sense from a geographical perspective, but I really like the guys in Phoenix. Maybe Phoenix and Atlanta.
We're going to have a little downtime around 1AM CDT this Sunday to replace the failed drive. Should only be around 15 minutes assuming all goes well. If all goes wrong, could be a couple of hours. I'd place the probabilities at about 60/40.
Running and double-checking backups right now.
Update: Ran a little late and a little long and a little hiccupy, but all done now.
Update to the update: And then when all was said and done, the network decided to notwork: The switch lost track of all our IP addresses and effectively null-routed the server. Had to manually bind them directly to the network interface, then restart the virtual servers one by one.
Had a drive failure1, which caused the system to reboot2, which caused a lengthy filesystem check because we'd been up so long3, which when circumvented allowed us to boot cleanly, which highlighted a networking glitch4, which when fixed allowed us to find the database corruption5 which we've now fixed allowing us to get back on the air.
I was supposed to be in a conference session on hosting web applications right about now...
1 Grrr Western Digital! 6 2 Grrr Adaptec! 6 3 Grrr ext3 default settings which I didn't bother to override...6 4 Grrr OpenVZ! 6 5 Grrr MySQL! 6 6 Though it must be said that we've been running on this without a hiccup for nearly 18 months.
Posted by: Wonderduck at Sunday, August 21 2011 10:12 AM (o45Mg)
2
I am sorry to bring it up in view of quick and successful resolution, but you should not keep two DNS servers on the same subnet. Run "host -t ns mee.nu" and "host -t ns zaitcev.us" to see what I mean. My secondary is not just on a different subnet, it's on a different continent.
Posted by: Pete Zaitcev at Sunday, August 21 2011 02:36 PM (9KseV)
3
Agreed. I had secondary DNS on a little VPS at another provide, but then the host node fell over and was down for 20 hours, during which time I moved it to the main server and never got around to moving it back.
Posted by: Pixy Misa at Sunday, August 21 2011 06:02 PM (PiXy!)
4
"...it's on a different continent" --- yes, but what if an asteroid takes out the planet? How will the astronauts on the ISS get to your web site after that? I plan to put DNS servers on Luna, Phobos, and Io. Just in case.
Posted by: dkallen99 at Monday, August 22 2011 12:50 AM (HOXKi)
I'll buy Seagate or Hitachi, even (ugh) Fujitsu, before I buy something from WD.
Posted by: Blacque Jacques Shellacque at Monday, August 22 2011 10:53 AM (PaYgs)
6
Hey Pixy, I have a new idea on fixing spam at AoS, but I don't want you to ban me, and I don't want to humiliate myself in front of internet great Steven Den Beste again(is he still around?)
So let me write my idea here, and you can quickly delete it once you've read it. Thanks in advance for not banning me.
Here it is. We all know that 'captcha' sucks. But what if you added captcha for any comment that included 3 or more hyperlinks? You'd catch 100% of the spam, and maybe half a percent of the nonspam. You'd win, aussie! Oi!
Posted by: Kevin at Thursday, August 25 2011 09:57 AM (PjWPp)
7
Yeah, some sort of captcha when there's something unusual going on - too many links, too many posts an hour from a given IP - that could definitely help.
Posted by: Pixy Misa at Thursday, August 25 2011 02:15 PM (PiXy!)
Youtube video, custom size, including the extra 30 vertical pixels the player uses: [youtube=5_sfnQDr1-o size=400x255]
Youtube video, custom size, not including the extra 30 vertical pixels - the BBCode engine detects if you've entered something that works out to exactly 4:3 or 16:9 and adjusts the player size appropriately: [youtube=5_sfnQDr1-o size=400x225]
If you mess up the size it still works: [youtube=5_sfnQDr1-o size=400x224]
Specify just the width - assumes you want 16:9: [youtube=5_sfnQDr1-o size=540x]
While in fact it's Wintertime here at Pixy Labs (and it's bloody freezing - or close to, anyway), I've just spent a couple of hours dusting off the main mee.nu site and I'm going to be posting there again. In fact, I'm going to try posting there every day. Even if it kills me. Which it probably will.
Going to put up a new banner too. I can recycle the current one next month anyway.
Well, on the plus side, the "more" tag worked this time.
Posted by: atomic_fungus at Friday, April 23 2010 01:13 PM (Rcclv)
4
Yeah, I can't reproduce the bug with new posts, so I think it's an issue with posts created with an earlier version of the software - I need to run a database cleanup.
I'm going to get a copy of the database and test my cleanup code, and if it looks good I'll run it on the live database this weekend.
Posted by: Pixy Misa at Friday, April 23 2010 03:34 PM (PiXy!)
Since you're working on this stuff anyway, here's another that may have fallen through the cracks:
If you take a post which has comments and change its category, then when you open the category listing that post will be there but its comments won't be.
Posted by: Steven Den Beste at Saturday, April 24 2010 02:40 AM (+rSRq)
6
Huh. That really, really shouldn't happen. The way things work behind the scenes should make that unpossible.
I'll take a look.
Posted by: Pixy Misa at Saturday, April 24 2010 03:15 AM (PiXy!)
7
And while we're hunting down esoteric bugs, something in Wonderduck's page format prevents me from clicking on any main page links from my Droid's browser. I can only assume it's using a specially modified version of Chrome, but it doesn't seem to happen at Chizumatic or at my own place.
Well now that's odd... Clicking a link in his sidebar worked, then after retreating to the main page, all the other links worked. Some confounding combination of formatting and browser?
Posted by: Will at Saturday, April 24 2010 05:35 PM (3BrvJ)
We'll be moving to our shiny new server this Sunday at 6PM Sydney time - 8AM GMT, 4AM EDT, 1AM PDT. So a mostly convenient time for most people - in the evening for me, and in the middle of the night for almost everyone else.*
Downtime is expected to be 30 to 60 minutes, depending on exactly how long the network switch takes to refresh its ARP cache. All URLs, logins, and IP address will be unchanged; it should just go offline and then come back an hour later on the new server running (up to) twice as fast.
Update: Pushed back one day and bumped. My test migration worked perfectly, but I only got there half an hour before the real thing was scheduled to happen, so I'm putting it off until tomorrow.
* 8 o'clock on a Sunday morning counts as the middle of the night according to ISO 8833.7.
Posted by: Pixy Misa at
05:37 PM
| No Comments
| Add Comment
| Trackbacks (Suck)
Post contains 161 words, total size 1 kb.
Friday, July 17
One Last Outage - Around 1AM CDT
Today's outage is proudly brought to you by Adaptec - "The number one name in overpriced RAID controllers with crappy firmware" - and Western Digital - "Our drives are so tough they eat other disk drives! Also, your data."
This is to replace the insane drive and wipe and rebuild the corrupted RAID-5 volume. Should be about 15 minutes. Once it's done, everything should be good - we have a RAID-5 array and a RAID-1 array and an enterprise SSD for the databases. What could possibly go wrong?
...
No, thanks, I don't want a list.
Update: DONE!
Update: And for some bizarre reason, after the maintenance was done and I'd made sure everything was working correctly, the networking went notworking. Bleh.
Posted by: Pixy Misa at
02:13 PM
| No Comments
| Add Comment
| Trackbacks (Suck)
Post contains 129 words, total size 1 kb.
Friday, June 19
And We're Back
I said half an hour, and half an hour it took!
Update: Except that my clever trick of redirecting the reverse proxy to minimise downtime caused the spam filter to block, um, everyone.
Most people should have picked up the DNS changes by now and won't have that problem any more.
Posted by: Pixy Misa at Saturday, June 20 2009 12:58 AM (PiXy!)
3
Big Daddy Pixy? I don't know if it's just me or what, but ever since the upgrade I've noticed two perhaps-bugs.
1) If a spam-comment is put into a thread, it gets blocked but the comment count increases. Clicking on "comments" to read the thread opens... nothing.
2) I've been experiencing a huge slowdown on all mee.nu/mu.nu blogs, including my own. It takes 20 seconds to open the "add link" or "add image" windows in the editor, not to mention just trying to visit a blog.
I know it's not on my end, because non-mee/mu.nu sites open just fine and I'm able to download things at my normal rate.
Thanks for all your efforts, Pixy ol' saint!
Posted by: Wonderduck at Sunday, June 21 2009 09:20 AM (hlGBx)
4
#1 is a known problem. I need to fiddle with that.
#2... Um. I haven't experienced any problems. Hmm. Hrm. (Just tried the linky thing there.)
Could you open a Command Prompt window, and do the following:
ping ai.mee.nu ping wonderduck.mu.nu
And let me know what IP address it finds for each one? Maybe you're still going to the old server and getting redirected to the new one every time.
Posted by: Pixy Misa at Sunday, June 21 2009 09:34 AM (PiXy!)
Cache cleared. If I go to a mu/mee.nu site directly, it loads fairly swiftly, but if I follow a link (say, via my blogroll, or Steven's), it crawls.
The "backstage" pages at The Pond are still crawling.
I'm experiencing the same thing on three different browsers: Firefoxy 3, IE7, and whatever browser it is that AoL uses these days (some variant of IE).
Posted by: Wonderduck at Sunday, June 21 2009 05:26 PM (8kQ8M)
10
Huh. That's seriously weird. Let me have a think.
Posted by: Pixy Misa at Sunday, June 21 2009 08:27 PM (PiXy!)
11
It all still works, it's just slow. I used dialup until October 2007, I can deal with this until it fixes itself or you work your usual magic!
Posted by: Wonderduck at Monday, June 22 2009 03:53 AM (hlGBx)
The on-again off-again mee.nu server move is on again, for this Friday at 6AM GMT.
Posted by: Pixy Misa at
07:09 PM
| No Comments
| Add Comment
| Trackbacks (Suck)
Post contains 17 words, total size 1 kb.
Monday, June 08
Mooving
mee.nu (and the mu.nu Minx blogs) will be migrating across to its new home on Monday at 6AM GMT.
Was originally scheduled for Sunday at the same time, but I somehow slept through all of Saturday, so I'm not quite ready yet.
Downtime is expected to be about an hour. Originally it was going to be just a few minutes, but due to recent hiccups I'm now planning to do a full database reload, so it will take a little longer.
Update: Running a bit behind schedule, bit still planning to do the move today. I have worked out a plan to minimise the downtime, so when your blog goes blank for twenty minutes or so, that will be it.
(I should be able to put up a message saying what's happening.)
Update: Still working on it. Tidying up the old environment now so that I can do a nice quick move. While I'm doing that, I'll do a test run of the database load.
Update: Downtime should be only about 15 minutes. The trial run took 3.5 minutes to dump the database, 1 minute to copy across to the new server, and 8.5 minutes to load. That's not at all bad.
The setup is nearly ready, so I'm going to proceed and get it done before the database glitches again.
Update: Damn. The database dump doesn't work correctly if there are corrupt indexes, so I'll have to do an index rebuild first, then dump.
Update: Ran into a bug. Looks like it's not happening today after all. I'll keep working on it and reschedule, probably to tomorrow.
Update: Doh! I know what's going on. Hang on...
Update: Nope, that wasn't it.
Weird. I'm already running a CherryPy app in production on this server, so why won't this one start? I can't even get a trivial sample program to run. Same version of Python and CherryPy too. Hmm.
Update: Foo. Networking wasn't running correctly on the newly-created virtual server. I restarted it, and everything is fine. It looked like a firewall issue - with the new system, not only is the server protected from the outside world, but all the virtual servers are protected from each other, and, in fact, from themselves. But no, it was just that the loopback interface wasn't running.
Update: Okay, looks like the application server and database are working fine now. Just need to set up the load-balancer. But it's nearly midnight, so I won't be doing the move today; it will be tomorrow instead.
I've reached the quiet spot between frantic preparation and even more frantic bug-fixing, where the files are doing their final update. Back to panic mode in 3... 2...
All finished! Not too much pain involved, either. Just waiting for the DNS changes to roll out now.
The server encountered an internal error or
misconfiguration and was unable to complete
your request.
Please contact the server administrator,
webmaster@blog.mu.nu and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.
More information about this error may be available
in the server error log.
Additionally, a 404 Not Found
error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.2.11 (Unix) mod_ssl/2.2.11 OpenSSL/0.9.8e-fips-rhel5
mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
PHP/5.2.9 Server at blog.mu.nu Port 80
Posted by: Susie at Saturday, May 23 2009 09:08 PM (SFNt4)
Hi Pixy, I have a question about the server you described over at Ace of Spades HQ —
“a dual-processor quad-core hyper-threaded Xeon E5520 with 24GB of RAM, a 4TB RAID-5 array (using an Adaptec 5805 controller), a 32GB Intel X25-E SSD, redundant power supplies, and a gigabit internet connection, running CentOS 5.3 and OpenVZ.”
— Does this server host all of your mee.nu sites, or just Ace?
Thanks!
Posted by: CTN at Saturday, May 23 2009 11:52 PM (hJ2AD)
4
It's to host all of mu.nu and mee.nu, replacing three smaller servers. Ace is just one of the biggest sites and was going to be down a little longer because I had to set up the comments server separately, so I posted an announcement there.
There's a second, smaller server in the new arrangement - a quad-core Xeon 3230 with 2GB of RAM - but that's mainly for test and development. I got that because it came as a special deal with 4TB of bandwidth that I can pool with the main server - for half the price of the bandwidth alone.
Posted by: Pixy Misa at Sunday, May 24 2009 12:00 AM (PiXy!)
5
My next question isn’t fair, primarily because it’s none of my business . . . . but . . . how do you make money hosting sites for others, for free, when it requires you to maintain oodles of hardware and software, with no ostensible returns?
Posted by: CTN at Sunday, May 24 2009 12:19 AM (tyVJj)
Posted by: Pixy Misa at Sunday, May 24 2009 12:33 AM (PiXy!)
7
Clearly, I should have opened my reader before my site this morning. Thanks for all your hard work!!
Posted by: pam at Sunday, May 24 2009 01:29 AM (l6NIn)
8
Thanks, Pixy! Main menu good--blacklist not so good: "An error occurred: Byte order is not compatible at blib/lib/Storable.pm
(autosplit into blib/lib/auto/Storable/thaw.al) line 415, at
lib/MT/PluginData.pm line 28"
Sorry to be such a pest!
Posted by: Susie at Sunday, May 24 2009 02:51 PM (SFNt4)
Okay, it's still in internal alpha testing, but after I ripped out its internals to provide for some of the major new features (scripting language, API support, safe third-party applets) it's been kind of broken for a while.
Now it's working fine, and seems to be at least close to the speed of 1.1. I can optimise the common cases of my new tag dictionary class, which is very heavily used; that should help things along.
Hmm.
Before:
108kb generated in CPU 0.13, elapsed 0.1315 seconds.
65 queries taking 0.0324 seconds, 276 records returned.
Powered by Minx 1.1.2-beta.
After:
106kb generated in CPU 0.12, elapsed 0.1285 seconds.
70 queries taking 0.0426 seconds, 279 records returned.
Powered by Minx 1.2-alpha-c1.
But I just noticed that recent comments aren't working on 1.2.*
Based on the work I've been doing at my day job over the past year, I do have some neat ways to potentially speed up the query side of things (and reduce the number of queries). But that's only one third the total time, so Amdahl's Law applies in spades.
* Doh! It's that blasted cross-referencing indexy thing I implemented. Efficient, yeah, but if the cross-reference table is empty it don't work. And if the cross-reference table isn't accurate, it don't work right. I'll have to find - or rewrite - the code to rebuild the index, but at least I know it's not a bug. As such.
Posted by: Pixy Misa at
11:08 PM
| No Comments
| Add Comment
| Trackbacks (Suck)
Post contains 244 words, total size 2 kb.
Friday, November 14
Can You Feel Anything When I Do This?
Let's see what happens...
Well, it kind of works. (See below.) Say bye-bye to half my CSS settings, and at the same time, half the markup in the document itself, but other than that, it's readable enough.
That's the documentation for one active tag (albeit one of the more complex ones). And it's pretty terse and short on examples.
As of 1.2b3, the current development version, Minx supports 1651 active tags. (I have no idea how many data tags there are - closing on a hundred thousand, I expect.)
Of course, most of those tags are variations or combinations or or specialisations or refinements of other tags, because Minx has only about 23,000 lines of code.
But if each tag needed a paragraph of explanation, that would fill a phone book.
So I need to take what I've been writing in Word, parameterise it, and build it into a Wiki.
Fortunately, two of the features added in 1.2 are Wiki support and text macros, so I can do exactly that.
Posted by: Pixy Misa at Sunday, October 19 2008 03:33 PM (PiXy!)
3
If you've got a minute to look, I've somehow created a layout anomaly on my blog- probably by doing something I'm not supposed to(!). Rather than put the whole saga here, it's in this post (although you need to look at the main page to see the problem). The anomaly will be live until Sunday, then I'll be putting things back to normal. Thanks!
Posted by: Old Grouch at Wednesday, October 22 2008 10:59 AM (HE8Tk)
Just as a reminder, this series of posts is talking about features in the new 1.2 relase coming in April. These tags aren't available on the live system just yet; I've copied the HTML produced by the test system to demonstrate their effects.
A couple more toys for you to play with, in the form of the [video] and [music] tags. I'm cheating slightly to show them working here, because while the player is installed on the server, the updated BBCode engine isn't.
To start with something simple, the tag [video=/flash/NewCuteyHoneyOp2.flv image=/flash/NewCuteyHoneyOp2.jpg theme=dark width=480 height=360] produces this:
Friday, December 21
Fixed!
That bug that was logging people out at random - the same bug that occasionally gave you someone else's name on a comments page - has been found and fixed.
It's a CherryPy bug and not a Minx bug, so I'm going to see if it's been fixed in the new beta of CherryPy, and if not, file a bug report.
The only problem is that I spent three hours looking for a bug in my code before I turned my gaze to CherryPy.
Posted by: The Brickmuppet at Saturday, December 22 2007 12:12 PM (Fclht)
5
Here is a terribly minor glitch I hadn't noticed before. The lower margin of the post does not recognize images. That is, on a very short post, unless the lower margin is lowered via the ENTER key, the image spills into the post below it.
I first noticed it here. Of course the link won't show it bleeding into the post below
This is the case in Firefox, IE, and AOL.
This is a ridiculously easy fix of course...hit enter 'till the post lower margin is below the image. (duh!)
I only mention it because it might be a symptom of a bug of some kind.
I'll leave the relevant post unfixed for a day.
Posted by: The Brickmuppet at Saturday, December 22 2007 01:44 PM (Fclht)
6
Yes, I saw that on your blog. That's a weird one. It's a CSS issue, so it's time to go spelunking in the CSS docs again.
Posted by: Pixy Misa at Saturday, December 22 2007 05:23 PM (PiXy!)
7
Well, I went ahead and lowered the margin manually.
Posted by: The Brickmuppet at Saturday, December 22 2007 06:57 PM (73lWn)
8
I got around that problem by creating a spacer 1px high x 450px wide. Stick that in after any problem image (and any text you want to be adjacent to it), and everything squares up. Example: this post, spacer included after "Help!" (see source). Also this one.
Posted by: Old Grouch at Sunday, December 23 2007 02:01 AM (TTce3)
Any mu.nu users want to move to Minx, just comment here or email me (andrew -at- pixymisa -dot- net), and I'll make it happen. I've copied the post from Munuviana into the extended entry for more details. more...
Posted by: Pixy Misa at Saturday, September 22 2007 01:39 AM (PiXy!)
2
Sure, why not. I like my computer banner best... ;-) Please add my name to the list and your assistance will be GREATLY appreciated. I'm even up for you adding a ad if you would like. Though, I am a small time blogger so it might not be worth your time. But you have been very kind and I would love to help bring in revenue.
Posted by: vw bug at Saturday, September 22 2007 05:24 AM (FPOeI)
The Pond would love to be Minxified, and will be more than happy to have a small ad, if it'll help in any way. Being somewhat clumsy in the way of the backstage stuff, if you moved me, it'd be much appreciated.
Would it still stay wonderduck.mu.nu, or would the address change? It matters not, just wondering.
Thanks, Pixy, and happy b-day (I put a post up, but didn't comment here... oops)!
Posted by: Wonderduck at Saturday, September 22 2007 09:48 AM (qBCpG)
Yep, you keep your mu.nu address. Though that is what's causing a slight delay - the cookies aren't quite working because the same system is now running across multiple domains (I think). Should have it fixed today.
Posted by: Pixy Misa at Saturday, September 22 2007 02:45 PM (PiXy!)
Don't know if the request from another post made it, but I'd like to be moved. Please add the place(s) to advertise mee.nu you deserve the bucks after all the work you've done.
I also don't need Cpanel for a while so whatever place I'm in line... go ahead and move GM's Corner, http://gmroper.mu.nu and let's get that critter movin' along.
Posted by: GM Roper at Saturday, September 22 2007 10:53 PM (S60yG)
6
Damn those cookies... not only are they fattening, but one just can't live without them. I was wondering what was going on. :-)
Posted by: Teresa at Sunday, September 23 2007 12:49 AM (rVIv9)
7
Yes, sorry about that Teresa. Loaded up your blog, happy happy, everything works, except that you can't log into it.
Shouldn't be too much longer, though.
Posted by: Pixy Misa at Sunday, September 23 2007 01:27 AM (PiXy!)
8
Don't stress on my account Pixy... I'm always wondering what's going on. *grin*
Posted by: Teresa at Sunday, September 23 2007 02:08 AM (rVIv9)
Posted by: spacemonkey at Sunday, September 23 2007 08:32 AM (2AE9r)
10
Pixy, the register button in the banner is failing to appear (in internet explorer) at either mee.nu and at my site, just thought you might want to know. Also how in the wrold do I get the background of my sidebar to be white without having it also turn the page margins to white rather than blue?
Posted by: Raging Tachikoma at Sunday, September 23 2007 11:41 AM (Dr4C2)
11
Pixy--I went to the main menu at munu (http://blog.mu.nu/cgi/index.cgi) and I got this :
Can't load error template; got error 'Loading template 'error.tmpl'
failed: HTML::Template->new() : Cannot open included file
tmpl/cms/error.tmpl : file not found. at extlib/HTML/Template.pm line
1500 HTML::Template::_init_template('HTML::Template=HASH(0xa1cbad4)')
called at extlib/HTML/Template.pm line 1105
HTML::Template::_init('HTML::Template=HASH(0xa1cbad4)') called at
extlib/HTML/Template.pm line 999 HTML::Template::new('HTML::Template',
'filename', 'tmpl/cms/error.tmpl', 'path', 'ARRAY(0xa16e6d4)',
'die_on_bad_params', 0, 'global_vars', 1, ...) called at
extlib/HTML/Template.pm line 1049
HTML::Template::new_file('HTML::Template', 'tmpl/cms/error.tmpl',
'path', 'ARRAY(0xa16e6d4)', 'die_on_bad_params', 0, 'global_vars', 1)
called at lib/MT/App.pm line 302 eval {...} called at lib/MT/App.pm
line 301 MT::App::load_tmpl('MT::App::CMS=HASH(0x9be0380)',
'error.tmpl') called at lib/MT/App.pm line 189
MT::App::show_error('MT::App::CMS=HASH(0x9be0380)', 'Loading template
\'list_blog.tmpl\' failed: HTML::Template->n...') called at
lib/MT/App.pm line 259 eval {...} called at lib/MT/App.pm line 203
MT::App::run('MT::App::CMS=HASH(0x9be0380)') called at index.cgi line
27 eval {...} called at index.cgi line 21
'. Giving up. Original error was Loading template 'list_blog.tmpl' failed: HTML::Template->new() : Cannot open included file tmpl/cms/list_blog.tmpl : file not found. at extlib/HTML/Template.pm line 1500 HTML::Template::_init_template('HTML::Template=HASH(0xa117b10)') called at extlib/HTML/Template.pm line 1105 HTML::Template::_init('HTML::Template=HASH(0xa117b10)') called at extlib/HTML/Template.pm line 999 HTML::Template::new('HTML::Template', 'filename', 'tmpl/cms/list_blog.tmpl', 'path', 'ARRAY(0xa12fd5
', 'die_on_bad_params', 0, 'global_vars', 1, ...) called at extlib/HTML/Template.pm line 1049 HTML::Template::new_file('HTML::Template', 'tmpl/cms/list_blog.tmpl', 'path', 'ARRAY(0xa12fd5
', 'die_on_bad_params', 0, 'global_vars', 1) called at lib/MT/App.pm line 302 eval {...} called at lib/MT/App.pm line 301 MT::App::load_tmpl('MT::App::CMS=HASH(0x9be0380)', 'list_blog.tmpl') called at lib/MT/App.pm line 334 MT::App::build_page('MT::App::CMS=HASH(0x9be0380)', 'list_blog.tmpl', 'HASH(0x9bd4c6
') called at lib/MT/App/CMS.pm line 218 MT::App::CMS::build_page('MT::App::CMS=HASH(0x9be0380)', 'list_blog.tmpl', 'HASH(0x9bd4c6
') called at lib/MT/App/CMS.pm line 2129 MT::App::CMS::list_blogs('MT::App::CMS=HASH(0x9be0380)') called at lib/MT/App.pm line 251 eval {...} called at lib/MT/App.pm line 203 MT::App::run('MT::App::CMS=HASH(0x9be0380)') called at index.cgi line 27 eval {...} called at index.cgi line 21
Posted by: Susie at Sunday, September 23 2007 05:29 PM (OGAM5)
Part one of the theme builder - the part that does fancy banners as seen above - is installed, though I haven't activated it for everyone.
Parts two and three, which handle layouts and styles respectively, will go in tomorrow. That brings the total number of colour options available to 104.
That's not 104 different colours; that's 104 different things for which you can specify the colour. Each with a little popup colour selector.
Also, you can spell it "color" and it still works.
That's good news. I was worried that if my "u" key went on strike in protest of its heavy-handed abuse at the hands of the Queen's English, I'd have to start spelling it coloyewr.
Posted by: Will at Saturday, August 18 2007 12:47 AM (olS40)
My data module has a hook for each table so that I can add derived fields. It now dutifully copies the value of each colour into a corresponding color for your convenience.
Posted by: Pixy Misa at Saturday, August 18 2007 02:42 AM (PiXy!)
I was testing the new theme builder module on my test box (a good place for that sort of thing). It seems to work well, except that the first thing it does is rename and deactivate your header, footer, and banner templates and replace them with the new standard versions.
Which I haven't actually set up yet.
One good point: Turns out the system is actually still usable with the header, footer and banner templates all missing.
Posted by: Pixy Misa at
02:37 AM
| No Comments
| Add Comment
| Trackbacks (Suck)
Post contains 78 words, total size 1 kb.