Sidebar widget broke after last update

Hi Cotelouis,

I’m sorry to hear that. It looks like you created a custom HTML output template (widget-content.php) and placed it inside the FPW plugin’s views folder instead of in your current theme as the instructions state.

When this or any plugin is updating, files inside the “core” folders may always be overwritten. That is why plugin developers ask customizations be placed within your theme’s folder.

If your custom HTML output template does exist in the flexible-posts-widget folder within your theme, then we’ve got another issue to deal with. Let me know if the view is there but isn’t showing up.

Okay, I tried moving the file to a flexible-posts-widget, but no matter what I name in the template file field in the widget, it’s still looking for the file in the plugin’s views folder. I don’t see any other settings where I can change this.

I’m not sure if we’re communicating clearly here. In your site’s folder structure, you should have: /wp-content/themes/[your-theme]/flexible-posts-widget where [your-theme] would be the folder of your currently active theme.

Inside that folder would be any custom templates you’ve created. So, if I have a template named my-widget.php the path to that file would be: /wp-content/themes/[your-theme]/flexible-posts-widget/my-widget.php

Also, you could try to remove any setting for the custom HTML template from your widget, just to see that the widget is getting the output from the default template properly.

I can guarantee that the custom template functionality is working correctly. I’m using it on many sites currently and I have updated them using the same process any others.

That was absolutely clear, and that’s exactly where I put my template file (wp-content/themes/Christos/flexible-posts-widget/widget-content.php

I tried removing the template name from the widget and saw linked titles in my widget space on the site, which I believe was how the original template was displaying the results, before I customized my own template.

Unfortunately, the path you’re using doesn’t appear to actually exist. If I try to directly visit your template file, I get a 404 error, not a blank page as should be the case if the file actually exists.

Reference accessing the default template or forbidden views folder within the plugin.

Since I haven’t heard back, I’m going to close this topic. Please feel free to repost if you still have trouble. Cheers!