Hotwiring the fragment-links and superceding the binary— binary— binary— binary— binary— binary— …

Posted by @ 11:06 am on Sunday 4th May, 2014.

If only I could do that, the task of editing all of the blog's image, image-link and mouseover URLs (to reflect the changes associated with migrating all of my pics out of the failing SmugMug and into WordPress) would probably be a doddle. As it is, it's a tedious manual-edit jobbie that's taking me ages.

Two months in and I'm still not a quarter of the way there. It didn't help that a fortnight ago WordPress updated to version 3.9 and the thing fell apart because of the limitations of the bundled "upgraded" TinyMCE visual editor which had been gelded of various features that I need to do the editing. The techies at BlueHost did a restore from a their monthly backup to get me back onto WP3.8.3 with the previous TinyMCE... that put me back in control, but it undid a month of editing and scrubbed a month of uploads.

So, expect this place to be a mess while the transfer is in progress. I reckon I have about 6,000 URL edits still to do, so it's going to take a long time.

FWIW, I did try reversing the polarity of the neutron flow but that had no beneficial effects. The sonic screwdriver...

is helping a bit.

Maybe I need a Doctor.

Related Posts Plugin for WordPress, Blogger...

7 Responses to “Hotwiring the fragment-links and superceding the binary— binary— binary— binary— binary— binary— …”

  1. geoff says:

    That sounds like a real chore. 😕
    I've just moved to WordPress from Blogger thankfully that was quite easy.
    You can now find me at 😀

  2. BG! says:

    @Afootinthehills - Well, for starters the SmugMug customer service, which used to be excellent, is now shite.

    As for functionality, the "new" SmugMug, introduced in Summer 2013, doesn't allow users to use the javascript customisations that the previous version allowed, SM went for CSS customisation instead, so anyone with javascipt customisations found their sites trashed after migration.

    Also, whenever SM change their software it usually affects the front-end, ie the bit that the rest of the world sees. That means that CSS customisations can be broken, and that SM can, whenever they want and without consultation or notice, change the look of what we create.

    Furthermore, there are bugs, introduced during the "new" SM rollout, that still haven't been fixed nearly ten months later. The list goes on and on and on... take a shufty at the Dgrin forum and you'll see what I mean.

    Here are a few starter links:

    I'll stop now, life's too short.

  3. BG. Thanks for the detailed reply. I use Smugmug mainly for storage so all the technical problems don't affect me, as far as I can detect at any rate, though I have noticed that thumbs sometimes don't load very quickly on the new version. Thanks again.

  4. BG! says:

    @geoff - That's a wise move, Geoff. I'll update all links to your site when I can.

  5. BG! says:

    @Afootinthehills - See, today we have a new example of how SM ride roughshod over paying customers' site-designs (post #64 onwards). The latest "fix" introduced a dumbfuck scrollbar into the middle of the info area at the bottom of the lightbox view. If a WP upgrade did such a thing I would be able to downgrade via backup. With SmugMug there's no such facility, paying customers are stuck with whatever SM foist upon them. It's shite.

  6. BG! says:

    @Afootinthehills - Here we go again... SM "just pushed out a massive update to the image editing tools" and it's a clusterfuck - see Tools in Organizer...b0rked?

Have your say - submit a comment

THE SMALL(ish) PRINT... (updated 23/07/2016)

By submitting a comment to this blog you grant me permission to reproduce its content and to reproduce the submitted name/URL in attribution. I will leave your content in its intended place and in its unedited form unless one or more of the following apply:

If you ask me to modify, move or delete your content, I’ll consider making the requested change(s) so long as there’s no significant alteration of the context of the content or of any debate associated with it;
If you change your email address or URL, I’ll update these details in older comments so that I'm not displaying dead links;
If I decide to change the theme or layout of this blog, thus affecting the placement and/or visibility of comments, I’ll make whatever changes I see fit for the smooth running of this blog;
If any comment contains insulting profanity or other content which I deem to be causing or likely to cause trouble, I’ll edit or delete as I see fit for the smooth running of this blog. I’ll try to remember to display the reason(s) for whatever editing I do, so that folk aren’t left hanging wondering what happened and why. If you can at least try to "disguise" your swearing, it would be much appreciated.

Other things to consider:

Comments must contain at least 3 characters;
You can use some code in comments, feel free to give it a shot and see what works;
If adding pics, the recommended maximum dimension is 600px.;
Comments containing many links will be held for moderation;
I reserve the right to amend this policy in line with proven applicable current legislation;
Free Speech: you may well have the right to it, but you've no right to compel me to a) listen to it, or b) publish it!