Doug Stewart

Peter:
That’s a direct link to a file. There’s nothing I or WordPress can do to natively catch that. Your webserver (IIS, Apache or NGINX) would have to know to catch requests for attachments and then figure out how to route them, which is well outside the scope of a theme’s capabilities.

You’ll need to change the way you’re embedding images in your posts — when you upload an image, choose “Attachment Post URL” under “Link URL” when you insert into post.

Make sense?

If you’re using a child theme (you should be!), just create an attachment.php with that code in it and WordPress will parse it correctly.

I don’t supply an attachment.php page with Elbee Elgee, thus it falls back to the template hierarchy to determine which page to use. It falls back to single.php in this case.

What sort of question do you have about it?

I’ll consider it, but I think it may actually be plugin territory, thus I may well just remove that section entirely.

Thanks!

OMatthew:
That code is in includes/functions/hooks.php and it calls the_time('F jS, Y').

What plugins do you have active? I’m thinking something is interfering with the_time().

I’m trying to figure out why this ended up in my theme’s support area — it doesn’t seem to be theme related at all.

[Theme tag removed]

Ahh, cool.

Do a full cache clear/page refresh to make sure that the JS is properly being pulled in.

RichardWPG:
Not quite sure why you keep posting that link. It’s not appropriate to this discussion — this is a legitimate bug in the code.

As I said above, line 139 in elbee-elgee/includes/functions/buddypress.php.

Committed. https://bitbucket.org/zamoose/elbee-elgee/changeset/b9667dd3f055

I’ve got a few more issues to roll up in a 1.3.8 maintenance release before I tag it and send it to the theme repo, so please consider this notice to go ahead and patch the file yourselves, as I have no idea how long the theme review process will take this time around.

Thanks!

Boone sorted us out:

https://buddypress.trac.www.ads-software.com/ticket/4449

I’ll be issuing a patch soon, but the core problem is that lblg_bp_init() is firing too late. Boone had me move it to after_theme_setup instead of widgets_init and, at least in my testing, it works.

To get this working, change line 139 in includes/functions/buddypress.php from

add_action( 'widgets_init', 'lblg_bp_init' );

to

add_action( 'after_setup_theme', 'lblg_bp_init' );

Save it and then you should regain functionality.

I’m the theme author, and it’s a bit more complicated than that. I’m directly importing BuddyPress’ AJAX handling code and it’s not working on BP 1.6. Boone, Pgibbs and JJJ all know about this via a Twitter conversation and we’re looking into a fix.

This is definitely a bug. I’m working on a fix.