Tag Archives: software

WordPress, missed schedule, and why I don't run my own server

The PolyBlog
January 4 2017

The other night, I was browsing my posts list in my admin panel on the website and noticed something odd — my scheduled post for yesterday morning didn’t actually post. And right next to it in the internal WordPress admin panel was a nice little red warning called “missed schedule”. I had seen this before and thought it was just a glitch, no biggie — just click publish now and it goes live. No problem with the post, it just didn’t go live when it should have. I don’t often schedule future posts when I’m writing detailed posts, although I might change the time stamp to 8:00 or 9:00 in the morning even if I’m writing it at 1:00 in the afternoon, like now. Just a small quirk I do to manage an indexing protocol that checks the time stamp, no real reason.

However, from time to time, I will write a bunch of posts all at once, and I want them spread out over several days. So I “schedule” them for future publication, usually 9:00 in the morning. So, the question was, “Why didn’t they post?”.

Running around the WordPress community

As with most glitches with WordPress, one is often not the first person to encounter it. Simply googling “WordPress Missed Schedule” brought up a whole series of people who had the same problem, posed the question online and had people respond. In most cases, their problem was slightly different in config once I scratched the surface, or the solutions were a bit different than what would seem to fit my situation. However, they did send me looking into several plugins.

I tried a plugin called WP CRONTROL that wasn’t a fix so much as a way to glean some additional diagnostic information. Namely that the small “glitch” was bigger than I thought — my CRON file was not running, and there were problems going back to August. Hundreds of behind-the-scenes happen on your website without your having to control them directly, little bots that can run from time to time, and your website software or the server software has ways to schedule them. Basically the same as your CALENDAR on your computer keeping track of reminders, etc., or even your regular WINDOWS update that does certain things at regular intervals. In this case, WordPress has a file that keeps track of all things it has to do (its own internal to-do list) called WP-CRON. I started trying to clean out the long list of expired entries but it would take forever.

So I added another cron manager called ADVANCED DATABASE CLEANER. Sure, I could have logged into the PHP admin area of my website and manually cleaned things in my database, but why would I do that when this plugin would do it for me?

Down the rabbit hole

I went down a rabbit hole after that. Lots of little tips and tricks everywhere, but few that were specific enough to help me, nor even in a good logical fashion. More like eight hundred people playing hunches and trying something on their server, some with luck, some with none. I jumped the queue while I was working through some of the options and started chatting with the Server Customer Support Rep, but honestly, their Tier 1 people are more about sales than they are tech support. They do okay, but this is way beyond them.

What I often find helpful though is that explaining the problem to them seems to crystallize it better in my own mind, and often triggers thoughts to try x or y that hadn’t occurred to me earlier or that I dismissed too soon. And it gave me a structure for understanding how to solve the problem.

A. GET YOUR DIAGNOSTICS

As I mentioned above, I used WP CRONTROL to see the list of cron activities and ADVANCED DB CLEANER to fix it a bit. WP CRONTROL also told me there was a 403 error (forbidden) on the WP-CRON file, but it wasn’t very convincing since some of the other errors might be causing it.

After going around the pole a few times, I found a great little tool called WP CRON STATUS CHECKER. It only has a few hundred downloads/installs, and it is a great little tool. The plugin doesn’t have a lot of info with it, but it adds a widget in your dashboard that tells you the status of your CRON files. It DOES nothing to fix problems but it does a quick test to see if WP-CRON can even run, and if not, tells you the status (403, etc.). I wish I had found this first. It told me for sure part of the problem was that WP-CRON was not running. And once fixed, you can deactivate it and leave it off. If you leave it activated, it will run on its own every 24 hours to check, but my site isn’t busy enough that I need that level of monitoring.

B. CHECK .HTACCESS

HTML sites have a small file in the directories called “HT access” that controls how visitors can access the individual files in the directory and subdirectory and is the second line of defense against people doing silly things like writing files and overwriting certain files on your site. On sites like WordPress, it’s the equivalent of a master security file that controls a lot of the subsequent access rights.

Some sites said to see if .HTACCESS was corrupted, but I was pretty sure mine wasn’t (I have other plugins that check the status of HTACCESS regularly, they would throw flags if it was corrupted).

What the sites FAILED to mention was that it isn’t just simple CORRUPTION that could be screwing up WP-CRON, it could be the actual proper setup is messing with it. I should have thought of that immediately when I saw the earlier 403 FORBIDDEN message in WP CRONTROL, but when I saw it again in the WP CRON STATUS CHECKER, I knew I had found my problem. Unfortunately, I did this step sixth or seventh instead of second!

The simplest way to see if .HTACCESS is your problem is to temporarily rename it something like .HTACCESS_TEMP or .HTACCESSXX. Then check the status again — if it was .HTACCESS causing the problem, the status will go green when you check after renaming it. If it is still red, move on to other options.

C. CHECK SECURITY PLUGINS

I run WordFence and iThemes, and of all the types of plugins, security ones are the most likely to cause access issues like above and conflicts with other plugins or activities. So, I temporarily deactivated them and then checked my other settings. Nope, still broken, so that was out.

D. CHECK OTHER PLUGINS

Anyone who has had a problem with WordPress, or really any CMS ever, they know that the simplest way to look for a conflict is to just deactivate all your plugins. Considering some people are running TONS of plugins, this isn’t often the favorite solution, but it’s better than turning them off and on one at a time. I deactivated them all, checked status, still broken.

E. CHECK FILE PERMISSIONS FOR WP-CRON

Of course, lots of people would say to check this one first — if WP-CRON is the problem, the “obvious” first step could be to check the file permissions on that specific file to see if the settings are wrong. Good logic, but since WP sets them in batches, the reality is that other files would likely have the wrong settings too and would have thrown red flags much earlier. Remember that this is a low-level file that only flags errors when it DOESN’T run.

For me, I temporarily changed the setting to 777, full read/write/execute and checked status again. Still broken.

F. CHECK FOLDER PERMISSIONS FOR WP ROOT DIRECTORY

I can’t say this would have occurred to me on my own. If WordPress is running, the folder must be set pretty close to right, or the red flags would be borderline catastrophic for failure. Never the less, it was still worth a try — again, I changed to full 777 rights, no change, still broken.

Why did I do all those things?

If all those had failed, I would have eliminated the three most likely internal problems:

  • corruption of access files;
  • access / permissions to the file or folder; and/or
  • conflict from security or other plugins.

That leaves you three other options that I’ve seen:

  1. Try a plugin called WP MISSED SCHEDULE. It isn’t on the main WP install directory, you have to do it manually from GITHUB. I’m personally leery of installing plugins that don’t reside in the WP repository, and on top of that, the installation instructions did not seem awesome for clarity. Lots of people have tried it and had it fail; others did it and said it worked; others said, “huh?”. I also feel like if the problem was any of the first five, this plugin would not fix any of those issues.
  2. Check with your host to see if there is a server config issue. Lots of people have said very simply, “Oh, it’s a config issue, contact your server”, but that is a bit too reactionary. If it is any of the above issues, the server people won’t know how to fix the problem either and unless you’re paying a lot for access to their tech support personnel, they’ll say, “Sorry, that’s a software issue, you’re on your own”. I used mine to get the ticket started, but I had resolved the diagnostic phase before we were done creating the ticket and I had figured out it was an .HTACCESS issue which they don’t help with anyway.
  3. Bypass WP-CRON and create a server cron file to do it at the server level. Yep, to me that’s as advanced as it sounds. If you google, you’ll see lots of people who have written why they don’t use WP-CRON, why they turn it off, etc. Almost all of them are hardcore techies who are totally comfortable running LINUX, the type who would thumb their nose at building a Raspberry Pi project as “toys for kids”. If you go this route, and you have access to CPANEL setup, it really is a single line to tell it what to run and when, but I confess it didn’t work for me, and I didn’t want to mess around too much in that level of direct intervention

You might note that I’ve also left out the nuclear option of reinstalling WordPress from scratch. Honestly, that is pretty low on the list of probable solutions if you have done an upgrade from a previously working version and haven’t mucked around with the configuration too much recently. It *should* work, and if it doesn’t, something else is likely configured wrong, not your basic WP install. Always worth a shot of course, and many people would say to start with that in the first place. Who would say to do that? Those who did everything else, failed, tried a fresh install and it solved their problem and now they preach purity of install. 🙂

So what does this have to do with running my own server?

All of these problems? And I’m only talking about a SMALL software config issue that sent me way down the rabbit hole. If I was running my own server, I would have another 20 possible causes, all having to do with either server configuration or potentially even a hardware issue. One of the “saving” graces to paying someone else to carry the load of managing / running a server with a large hoster is that the cost/benefit ratio to me is WAY in my favour, particularly the number of times a problem like this has frustrated the hell out of me. I don’t need that added stress in my life. And if others are running the same install just fine on the big server, I know it is MY problem, not a technical screw-up that I did in the server setup. Worth it’s weight in gold.

As for me, now that I know it’s an HTACCESS challenge, I can push it to the back burner. I can work around it for now, and at some point, I’ll fix it. For now, I’m leaving it alone.

If you ended up here while searching for a solution, feel free to let me know how it’s going in the comments!

Version 3.3 of my websites: the software side

The PolyBlog
August 18 2016

As I mentioned in my earlier post this week (Version 3.3 of my websites: the technical side of things), I have tried various applications to “run” the website. Early on, I used Microsoft FrontPage. Then I tried some out of the box HTML and ASP applications with names like GPEASY or EZ107. I eventually went bigger and tried various content management system (CMS) applications like Drupal, Joomla and even MediaWiki. None of them were quite right for me.

Some people have opted for commercial platforms like Blogger or WordPress.com and those were all viable options. But I always came back to running my own site with my own set of installs. I started small, I went bigger and bigger, I went up to a WordPress install, I dropped back, and then finally, I went all in on WordPress.

I would be the first to confess that it is WAY more power than I need. People run full company sites with this thing, including full e-commerce capabilities or thousands of users with forums and discussion groups.

Me? I need a blogging platform, comments, and just a bit of capacity to show videos and images. Occasionally I get fancy and run a poll or something, but mostly it is just me blogging and the sound of a dry lonely wind blowing across my front page, maybe with digital tumbleweeds rolling along. It is not high traffic. One of my favorite Pearls Before Swine cartoons suggests the one character’s blog would have more traffic if he wrote it in crayon on a bathroom wall, and that is probably true for my site. Once in awhile I touch a nerve and garner an uptick in viewers, particularly if I’m talking about HR or development. Other than that? Mostly me prattling on into the digital ghostlands of the internet.

Yet I still want that power of WordPress. As I mentioned in the previous post, I tried separating my various musing into two camps for awhile but my approach to my site was still pretty diffuse. Blogs I would write with a specific angle in mind on one site often would end up fitting better on the other site under a different heading. Not a big deal to move, just illustrative that my approach to my separation into two blogs was not very concrete.

And when I rearranged my setup into a single blog, I thought, “YES! This is what it is all about. Everything I write in one place. Awesome!”

However, I realized over time that it wasn’t quite as awesome as I had hoped. I post in bursts and spurts, often on a single theme. Someone looking for HR info doesn’t particularly care about the latest quote I might share or what’s going on in my personal life (sob). And the balance didn’t seem quite right at times, particularly when I started adding quotes or humour. So I started thinking again about separating the blog entries into two groups.

The first group is what you see here. The more personal side of my musings:

  1. Posts about family or just daily experiences…the truly personal side of my life;
  2. In the same vein, but a little less “directly personal”, some of my approach to life like goal-setting, learning including photography, and spiritualism;
  3. A science and technology theme, in that I will be writing more about astronomy (a hobby) and computers (mostly about this site, but not always); and,
  4. A general set of posts around humour, quotes, recipes, and a catch-all around “ideas” (often involving principles and current news items).

The second group of blog entries is over on my other site (polywogg.ca), although at the time of writing, it isn’t really properly formatted and set up yet. For these ones, the groupings are not quite as defined yet either, but they are my more professional topics as a writer:

  1. Of course, there is my main theme around Human Resources, and more specifically, my HR guide to federal competitions for jobs…I’ve considered even making this a theme for another single purpose site, but I don’t need to do that yet, and I’ve included the proceedings from an HR conference I helped organize with some friends from university;
  2. Key insights that I can write about, since I can’t write about some aspects of my work life, are around the role of the civil service, governance, and international development;
  3. I like writing reviews, and people seem to value them on Amazon and elsewhere, so I wanted to collect my book reviews all in one spot, along with musings on reading in general, and eventually expanding so that all my movie reviews, music reviews, and regular TV reviews are together too;
  4. I read voraciously at times about the world of publishing, and I have some views I want to share regarding publishing, marketing, pricing, and even the role of libraries in society; and,
  5. Finally, what probably pulls all of this theme together, I want a place to post some of my own writing — shortstories, maybe some novel excerpts, some non-fiction guides, etc.

The funny thing is that deciding all of that still left me with a major choice.

A choice of branding

Which site would be “PolyWogg” and which site would be “ThePolyBlog”? Technically, they are both PolyWogg, as they are both my musings, just on different topics. And I could certainly tell myself that if the first site had entries about my personal life and family, and I’m “PolyWogg”, it made sense that PolyWogg would be the one that was more personal.

Yet ThePolyBlog is a far more informal title than PolyWogg, and if I used the personal for PolyWogg, and put the HR stuff on ThePolyBlog, well, the guide isn’t really blog entries. Plus it would then make sense to call it “ThePolyBlog’s guide to …”, and that doesn’t sound right to me at all.

In the end it doesn’t matter of course, or at least not to any one but me, but it would be a major pain in the patootie to change it around later, so I wanted to try and get it right the first (well, actually the SECOND) time.

In the end, my wife cast the deciding vote. She felt that ThePolyBlog was more informal too, and PolyWogg did seem to be more about my writing normally. So the Blog title goes to the personal informal stuff (site 1 above) and PolyWogg goes to slightly more formal “public writing” (site 2 above).

I have to confess, I was a bit surprised by how easy everything divided up once the decision was made.

Making the move

Of course, making the move was more complicated than saying “site 1 is this”, “site 2 is that”. It was all on a GreenGeeks platform under PolyWogg.ca. I needed all that content moved to WHC.CA, and I needed it split.

In the end, I settled on a two-step move. First and foremost, I migrated EVERYTHING to ThePolyBlog temporarily. WordPress has some tools that help you move everything from one place to another, including the install, but since I couldn’t be sure the GreenGeeks site wasn’t all screwed up from the myriad of changes, I decided I would do a fresh install and just move the content. I had hoped to have both PolyWogg sites (old and new) running simultaneously and bop back and forth from one to the other while the new remained in sandbox mode, but that didn’t quite work out the way I had hoped (I would have had to play constantly with my HOSTS file, too much trouble).

So I did OLD POLYWOGG and NEW THEPOLYBLOG setups, got everything all moved over, tested, all the content fine, and then I deleted the old PolyWogg site, moved to a fresh install at NEW POLYWOGG, *and* what was really cool? I then just copied the NEW POLYBLOG content over into NEW POLYWOGG and started deleting the stuff I didn’t need from each.

I even got to play with plugins as I went to make sure everything was relatively identical. In the end, my goal is that the back-end will be relatively identical, it is just the content and names that will change. “My branding” will be relatively uniform across the two, just mild differences in colours and menus, etc.

Setting up the new WordPress sites

One of my goals in setting up the new sites was to completely clean up a bunch of old plugins that I might not need anymore while streamlining certain bells and whistles too.

As a small digression, I’m often amazed by the number of people who blog, “Hey, I use this great plugin called ACME WIDGETS”. Which is great that they want to promote something they like, but it also starts giving out information to potential hackers about how your site is set up, what it is running, etc. I break this rule myself as I say I’m running WordPress, but that isn’t that big a surprise — while it doesn’t say it on my site, anyone doing a VIEW SOURCE on any page would see WordPress references pretty fast. But I don’t feel like I should make it easy for anyone to tell them things they don’t need to know, so while I will talk about plugins, I won’t talk about their names, just about the functions I’m looking for…

  1. Obviously, one of the first decisions people make in their design is what theme to run. Lots abound, and most add functions I don’t need — sliders, magazine setups, etc. I’m a pretty vanilla guy whose posts revolve around words. A lot of words. I was using a theme that I subscribed to a long time ago, upgraded to pro, upgraded to a new version, upgraded to the pro version, now it is available in regular free mode and another pro version. The regular free mode is more than good enough for my uses. Not quite as “clean” looking as the previous one, but lower load time. It will easily meet my needs. And free is good.
  2. The second piece people need to think about is protection. No glove, no love, and that applies to websites too. Spam protectors, firewalls, login blockers, ongoing monitors, backups, and my personal favorite? Changing the default login page so that the bots can’t even find it to try and log in. Of course, if you screw up or forget where you hid it, you can get locked out too. Oops. 
  3. My next set of tools are around beefing up the look and feel from the default theme options to add a few bells and whistles. For me, this is mostly around adding some custom widgets, some better page navigation, maybe a tool for polls and charts, and even ones around helping identify other posts that are like the current one to help encourage people to stay on your site longer.
  4. Of course, if you don’t write anything, there’s nothing to see. So I added some basic tools for improving the writing and editing experience, adding in shortcodes to simplify certain functions, making it easy to clone or copy posts into a new post, and even controlling how quotes look/work and adjusting how many revisions to keep in the database.
  5. One of the hottest categories in the plugin world is social media, but I keep mine pretty basic — some simple sharing links, something to help with printing, adding in some contact forms to make it easy to contact me, improving the way links are done, and just for fun, tweaking integration with major sites like Twitter and Facebook.
  6. I added some functionality to one site to allow me to more easily facilitate downloads of some documents, but mostly I am more about the back-end — statistics, word counts, checking for broken links.
  7. Lastly, I add a few plugins that are usually not active, but help me with certain functions you have to do from time to time like managing a database, optimizing setups, or in the case of the “big move”, duplicating and importing another WordPress site.

The agony of defeat, the thrill of victory

One of the reasons the “move” went well is that I made a painful decision a few months ago. I finally accepted that part of the frustration of the last few years with my site has been constantly trying to integrate my large photo and video gallery into the same workspace. Sure, WHC offers galleries too, and like most hosters, block video hosting (you can import links, but the files have to be stored somewhere else). In the end, I bit the bullet.

I moved my photos and videos to SmugMug. It has been the best decision I ever made. Of course, if/when SmugMug goes under, I’m screwed, but in the meantime, it is working flawlessly. Videos, pictures, all together, easily controlled, nice layout. It just works. And allowed me then to concentrate on addressing more gaps in years processed than in figuring out which plugin or theme wasn’t working. I wish I had it working well in a self-hosted site, but it was just sucking too much time to get it right. We recently had a birthday party for a 90 year old member of our family, and I put a whack of photos all up on the site, ran the app, and voila, instant slide show for the party. Worked great.

For the first time in several years of trying, I feel like I’m organized for processing photos.

However, with the pain of the move, and the thrill of it working, I then moved into the renewed pain of fixing my WordPress site for photos. I know what you’re thinking, “Wait, you put everything on SmugMug, didn’t you?”. Of course, I did.

But some of my blogs LINK to those photos and use them in posts. This means all the old links for any photo in my OLD SITE which pointed to a page on my self-hosted site now point to dead links — I had to re-add all my photos back into my blog entries.

Mostly these were entries where, for example, I talked about my honeymoon, and what I was putting in the blog were samples of the things we saw as we went. Almost like a trip blog with pics added. I tried a couple of plugins that were designed to make it easier to link, but it wasn’t required. After testing several methods, I realized that the link available on SmugMug integrated seamlessly into WordPress just by pasting a certain form of the link. It was almost instantaneously PERFECT. Really happy with it. What I thought would take possibly weeks to fix was all done in a couple of hours, and not very strenuous either — most of that time was re-reading the original blog!

Where am I now?

This site is basically done for layout and configuration. Which is why I’m blogging again. I didn’t bother blogging on the old site since back in May, partly as I didn’t know if I was going to be able to keep the content. Now that I’m up and running again, I’d like to get the word count on this site up to the 250K mark this year. Particularly now that I’ve fixed a small formatting glitch as two conflicting plugins tried to format the same text. Bye-bye to one plugin.

Now, on to fixing ThePolyBlog, a bit more challenging for some of the plugin tweaks.

Photobook fun

The PolyBlog
February 1 2016

So I’ve been spending a lot of time uploading old photos to my website, and now that I have a healthy base to work with, I’m working on some photobooks. Nothing too “fancy”, mostly just “year in review” type books.

I’ve used Shutterfly before, and while it puts out a decent book, I have two reservations with it. First, because they aren’t produced in Canada, you end up spending a heavy chunk of cash on shipping. Not exorbitant, just enough to notice. Price goes higher the faster you want it, as it would be anywhere.

Second, and a little more vague, the photo places often ship them overseas for production to Asia, and there is little regulation for either labour or the production methods used in a lot of the hot spots. We recently had a canvas print shipped from Malaysia (by Photobook Canada, not Shutterfly) and it came in smelling like musty canvas — turned out it was a lacquer they used on the finishing. There’s no way it would be allowed to be shipped in that condition in Canada, would never pass the sniff test, literally. The print stunk bad enough I had to put in the garage for a few days to air out. It’s relatively fine now, but not the most reassuring of experiences. And Shutterfly uses the same printing options/places.

On the plus side, they are reliable, they have regular sales, their coupons are stackable (i.e. 30% off for a sale, $10 off on books, free shipping etc. — most sites would make you choose one, Shutterfly usually lets you apply all of them to your order at once). I recently did a full year in review book with them, haven’t received it yet, but it has a LOT of extra pages (80+, when standard is 40) and price is about $75 in the end, including shipping, etc. Not great, not horrendous. None of the extra bells and whistles. And their software has a couple of painful omissions (an ability to duplicate or move pages, for instance). A solid 8 / 10 for sure on quality, software and price.

Mixbooks is the big blogger darling in the U.S. at present, with lots of people saying it is 10/10 for quality and software, maybe 8/10 for price. They are competitive with the other companies, but coupons are not stackable and their sales are not as frequent or as deep. I found the software good, but unwieldy at times. In the end, I bailed before completing an order.

Photobook Canada is one that everyone likes to say is better because it is supposedly Canadian, but the stats on their production in Canada are extremely limited. Most of their cheap stuff they farm overseas, maybe they used to do their stuff and prints here in Canada but looks like it is all off-shore now. The smelly canvas came from Malaysia, two calendars came from Malaysia. A small astronomy book I did awhile ago came from Asia somewhere. I’ve just ordered a small book as a gift, and I suspect it will also come from Malaysia. Software is not as good as Mixbooks or Shutterfly, but functional, and their cheap options are good for price at least, if not enduring quality.  Their other fantastic feature, in my view, is that their software is 100% downloadable. You can build the entire book on your own computer and just connect when you’re done. It takes a while for everything to upload at that point, but it’s better and faster than working in the cloud the whole time. I used them for the calendars (and make a rookie error with them) and the canvas print (that was initially smelly and is okay now), but I should also give them credit for the fact that my vouchers had expired (I didn’t realize they did that when I bought them last January), and they extended them with no trouble at all. Nice.

I checked out a bunch of other sites this week too.

Shoppers Drug Mart has a good basic option, software seems a little limited, and prices are okay but competitive. Their big “savings” offering is that it is free shipping to their local stores (I discovered their options earlier this week when sending some simple prints to a remote store). However, the software crashed completely in basic options working with both Firefox and Microsoft Edge. I’m not willing to invest any time in buggy software.

Uniprix seemed okay, nothing flashy. Basic software, prices were okay, seemed more geared to the pamphlet-style softcovers than some of the other bigger companies. I don’t know that I gave them a truly adequate test though.

Loblaws was a surprise for a couple of reasons. First, I didn’t know they had a photobook option — it strikes me if they were kicking butt, everyone would know about them. Second, their software is the SAME as Shoppers Drug Mart. Whoever is their backend supplier has given them the same front-end interface, with only minor differences. Seemed good, not as big and powerful as Shutterfly, Mixbooks or Photobook Canada, but decent enough. I even found some default templates I liked. But here’s the weird part…I chose a special template with some contemporary features i.e. not everything was blocky, squared designs. About half the default pages had a bit of a scrap-book feel to them, a common design feature. Except when I then went to the layouts feature to see what the options were for additional pages, none of those scrap-book layouts were available to select. All the rest were blocky, perfectly squared line ups. No obvious option to copy the existing templates either, unless I wanted to copy a page element at a time. But then it got even weirder…I chose a default template, added it to a page, and the photo sizes were completely wrong. I had the book set for 9×12″ size, and it put photos down as if they were going in a 6×6″ book. In other words, just part of the page…and no option to drag them as a group to make them bigger. You could manually adjust each and every photo individually. Nuh-uh, no way. That would be incredibly time consuming if I add some 50-60 additional pages, all of which required custom layouts. However, I have discovered that you CAN duplicate the original pages, just a bit of extra manual work to do it, kind of counter-intuitive.

Lots of people have used Costco and while I admire their commitment, the software was the worst one of all. Slow, few options, etc. If you had, say, 75 photos, and you wanted it to pre-populate them into a book template, it might be okay. But 10 minutes in and I’d already found 3 things I couldn’t do in the format. Not an option. Most importantly they had a lower limit on number of pages allowed. I was two-thirds of the way through a photobook when I came to a screeching halt — I couldn’t add anything else, and couldn’t copy the project to another project (I would have just split it into two books).

Henry’s has a site that has the same back-end as Loblaws and Shoppers Drug Mart (same themes, etc.) but a completely different interface. Looks okay, but it won’t actually let me load any photos from the album into the layout to try it. It didn’t want to sync with other sites either. Kind of hard to do a photo book if you can’t get photos into the layout! Fail.

I think I’m going to give the Loblaw’s one another go. We’ll see if it works out. Might try UniPrix after that, based on a friend’s recommendation. In the end, I’m likely to end up back with Shutterfly, but it won’t be for a lack of trying to find a Canadian supplier.