I’m not entirely comfortable giving you access to our control panel, especially as we’re not using a traditional CPanel set up (we use VestaCP).

I’ll send an email regardless.

Hey Catalin,

Appreciate the reply, but this doesn’t answer my question. The Post Settings meta box is no longer showing for Authors, only Editors and Admin. Previously I could edit:

td_templates_settings.php

by changing a line to allow users with “upload_images” permissions. If you see previous replies before user ‘soundstrat’ hijacked the thread, you’ll see my original issue and solution.

Hey folks, updated to version 4.8 and the file shared before is no longer there. Do you know where this code has moved to so I can enable the post settings box for Authors. (basically, anyone who can upload images).

Hey Catalin,

Sorry, this isn’t what I mean. I like the Gutenberg editor, it’s just missing a couple of the tagDiv-specific options when adding images into posts such as the “tagDiv Image Style” and the ability to choose “tagDiv Slider Gallery” is also missing.

Hopefully that makes sense 🙂 let me know if you’d like any more specifics?

Hey Catalin,

Thanks for the feedback, however this isn’t what I’m looking for.

Our site’s members are only those who write on our blog, signing up is closed to the public.

What I’m asking is whether there’s a way of pulling the URL from an author’s user profile after they’ve entered it. Specifically the “Facebook” entry.

If not, then no problem, I’ll figure out a way of doing it somehow!

Hey Catalin,

Is it possible to do this to just a single page?

Excellent, thank you!

That’s solved that problem 🙂

Hey Andrei,

I should have probably mentioned that our “Author” role doesn’t have the publish_posts capability (for security reasons), something which I’ve now discovered is needed in order for the Post Settings meta box to appear after a bit of testing.

Is there a way for me to edit the code to allow any user with the “upload_files” capability to see the Post Settings box?

Thanks!

Hey Andrei,

I can confirm that the correct Twitter name is being used in the user profile section as shown in your screen cap.

I’ll be sending you an email shortly.

Hello,

Ah, that’s fantastic to hear.

As I mentioned above, I’m new to Child Themes, so from now on I’ll be sure to keep an eye on compatibility with any new updates.

Thank you for your support.

Hey Chris,

Don’t apologise for butting in. This is personally my first experience with Child Themes as usually I’d edit the “main” theme as it were, but times before I’d tweaked so much, updates usually broke the site, leaving me to either revert to a previous version, or just to refuse to update the theme entirely.

I may consider your approach as I’ve barely touched this theme due to its many customisation options.

Thanks!

Final update:

Good news. I’ve fixed the problem.

It seems the new version of Newsmag has an updated td_module_single_base.php which is different to the one I’ve been using in the Child Theme. The reason I have that file in the child theme is because I followed this tutorial to hide the ads on a per-post basis:

https://forum.tagdiv.com/topic/function-to-hide-ads-and-function-to-show-author/

I have since copied the updated td_module_single_base.php and re-applied the above code found in the tutorial and things are back to normal.

I understand that this may be a totally incorrect use of the Child Theme, but it works! If you have any advice on how to better implement these changes then please let me know: aaron@n3rdabl3.co.uk

To quickly add to the above:

I received the white-screen when deactivating all of the plugins while the Child Theme was active, not the main theme. The main theme saw no issues when I deactivated all plugins.

Okay,

I forgot to mention that I’m currently using the Child Theme (as we’ve added a few customisations to the footer and functions.php)! I activated the main theme and found that the Featured Images have returned. I also discovered that deactivating all of the plugins (but Visualiser) caused the site to white-screen, so we’re looking into that at the moment.

It seems it’s entirely likely that some code we added to the Child Theme files have conflicted with the Featured Image. We’ll do some digging and update the post accordingly. Alternatively, I could send over the Child Theme files (via the email address you provided) to discuss things in more detail?