Darren_S

Thanks, Amrit. I did create the inc > widgets folder on my child theme, and made a copy of colormag-featured-posts-widget.php for Featured Posts (Style 1). But edits to this don’t do anything, as evidently this file does not take precedence over the parent theme. I have to make my edits to the same file in the parent theme … hence my reason for creating this thread.

Is there perhaps an issue with the theme path declaration somewhere? I’d love to just use the child theme if this particular widget file can take priority.

Thank you for the response. On the second point, what I’m looking for is which file (and location) in the parent theme to copy to my child theme that will let me customize the featured posts widget. In other words, where in ColorMag can I find the include statement for inc > widgets > colormag-featured-posts-widget.php?

Copying just this file to a child theme does not override the parent. (I’m having the same problem as Bob_the_Builder in the thread you linked, and you’ll see at the end of the thread that it is unresolved for him as well.) I’m not sure if this is because WordPress ignores includes, or if there is another reason. But I thought if I figure out where the widget .php is being called, or rewrite the function in the child theme’s functions.php to use the child theme’s directory, I might be able to get around the problem.

Just to follow up on this issue — As I don’t have a paid subscription I was going to follow up after my site was published, but in the meantime I’ve found the setting that was interfering with the widgets being used by the home page.

Evidently my home page setting (show latest blog posts vs. show a static page) were set differently in WordPress’s settings and in the Customizer for ColorMag. I presumed these were the same (that the Customizer was simply overriding the WP setting.) After I created a page and synchronized the two to use it as the home page, the widgets suddenly showed up and could be further customized.

Thank you again!

Thank you for the fast turn-around! I’ve updated the plugin and it the notice has been fixed.

Thank you!

Thanks, Barsha. The website is in maintenance mode for pre-launch development; is there another way I can give you troubleshooting access?

Follow-up, in case it helps with diagnosing why my home page is not updating to reflect widgets: I’ve just installed ColorMag on a different site. Leaving the theme inactive but previewing it in the customizer, I see the exact same layout on the home page there — one big news item that spans two columns, and two columns of headlines below it.

This is of course without changing any of the second site’s existing widgets or deploying any of ColorMag’s TC widgets.

This leads me to believe that Site #1, where the theme is active and the widgets are in place, is just ignoring the widgets altogether. Why might a new site with ColorMag active reflect the same home page layout shown in the customizer on a site where the theme is inactive and lacks the properly placed widgets?

Thanks for the swift reply. I figured as much. Since we have to worry about ignoring those files anyway, I’ll speak with my sysop about just moving everything else to /wp-content/gallery/.

Sandra: I ended up installing the “WP Downgrade | Specific Core Version” plugin to downgrade to WP 5.4 (and prevent automated upgrades).

It’s definitely a temporary fix, but because my offending plugin (MagicFields 1.x) is no longer supported I’m going to have to set aside a large chunk of hours to move to a different custom fields plugin and migrate all my custom fields data.

But sticking with 5.4 at least makes my site usable in the meantime.

Update: Installing the “Enable jQuery Migrate Helper” plugin has resolved all of my issues. (Read the plugin’s description to understand why. Prior to WP 5.5 this was apparently included in the core.)

After installing you’ll get some error messages in /wp-admin flagging any plugins that are using deprecated jQuery calls.

Update:

Installing the “Enable jQuery Migrate Helper” plugin has resolved all of these issues. (Read the plugin’s description to understand why. Prior to WP 5.5 this was apparently included in the core.)

In my case it was an outdated version of the Magic Fields plugin that was throwing deprecated jQuery errors, which impacts things all across the admin back-end.

(I’ve also learned through this that Magic Fields no longer releases updates through the WordPress plugin library! Yikes. Off to download the latest version of that plugin …)

I am experiencing these issues on the latest version of Chrome after the 5.5 update, as well as several other interface errors I’ll post to another thread.

Thanks for the swift response. In this case I am creating custom titles for multiple nested “Page” sections using PHP conditionals in the theme’s header.php file. (This is in part because Yoast doesn’t quite have all the title snippet variables I need, such as grandparent page title as well as several page-specific queries; and also because this was already implemented on the theme level before I installed Yoast.)

Is the Snippet Editor that you tested the one that appears on each individual Page editor (and not the global settings, as at SEO > Search Appearance > Content Types > Pages)? If so, how could I “touch” all of these site-wide without opening all 4,000 pages in the editor?

• This reply was modified 4 years, 4 months ago by Darren_S.
• This reply was modified 4 years, 4 months ago by Darren_S.

FWIW I am experiencing the same issue after re-authorization. This was evidently caused by FB’s security measures last week in which they logged out some 90 million users, invalidating our API tokens.

SNAP shows that I am authorized, and now even shows my list of groups I can post to … but I still get an error when I try to post.

Array
(
    [Warning] => 
    [Error] => Error validating access token: The session has been invalidated because the user changed their password or Facebook has changed the session for security reasons.
)

Note from this discussion that the issue may be on FB’s end, and not SNAP:

https://developers.facebook.com/support/bugs/1329476740516876/

Will do — thanks!