farnely

@quantum-leap
This isn’t the first time the developer/s have released a version containing basic coding errors and I doubt it will be the last. I got fed up of waiting for them to acknowledge the issue when I reported it let alone put it right and have now removed the plugin from my site. But thanks to you for sharing the solution.

That’s good news

I’m closing this ticket now; if anyone else continues to have any issues, please open a fresh ticket.

So, I’ve checked the content of the options field and mine looks like this:-

a:1:{s:12:"_multiwidget";i:1;}

I’m not displaying mine as a widget, I’ve just put the shortcode in the editor in WP Admin.

It occurred to me that there might be an incomplete div tag somewhere so I had a look at your PHP files. One thing struck me: on most of them your HTML is preceded by a closing PHP tag and then you PHP echo values within your HTML. For example, like this:-

<label for="text_color"><?php _e( 'Text Color', 'weather-atlas' ); ?></label>

In the file weather-atlas.php, however, you echo your HTML within your PHP. For example, like this:-


echo "<div class='weather_demo_wrapper'>";
echo do_shortcode( '[shortcode-weather-atlas selected_widget_id=' . $widget_id . ']' );
echo "</div>";


Personally, I like a consistent approach but it’s not my plugin and it shouldn’t affect the output. What is probably more of a problem though is that the opening PHP tag on Line 49 is incomplete; it reads <? instead of <?php.

Might I suggest you scrutinise your code thoroughly in case there are other instances of incomplete PHP tags and you might find a “<” or “>” is missing somewhere too.

Thanks for altering the SQL queries. My settings page is still OK now since I de-activated and re-activated other plugins & theme. Don’t know why that would make a difference. I’ve not had a problem with the shortcode output not showing.

This piece of code which appears in at least 3 of the plugin’s files (eg: line 52 in weather-atlas/admin/weather-atlas.php) doesn’t use a WP wordpress function:-
$widget_options = $wpdb->get_results( "SELECT * FROM {$wpdb->options} WHERE option_name LIKE 'weather_atlas_widget_%'" );

So, I took a backup, deactivated all plugins (except yours) & my theme, installed & activated default 2023 theme; no change in Settings. When I re-installed my backup, however, the Settings page is now fine!

What I would like clarification on though please is why you’re not using $wpdb->prepare for the SQL query that fetches the content for the Settings page.

Thanks.

totally agree – got a few other issues too (see separate ticket)

OK thank you; I’ll reconsider my approach.

The authenticate callback only checks the user’s role/capabilities (it’s not where the auth cookie is set). If the user is an administrator, they are redirected to the custom form which is processed using admin-post.php and runs a custom function and this is where the auth cookie is set using wp_set_auth_cookie.

Thank you for this; it’s been a great help.

Hi Alan

.htaccess was the only place I didn’t check and that’s what was causing the issue. Thank you so much for the quick turn round and pointing me in the right direction.

With an error like this, something won’t be working right somewhere so any timeline on getting this fixed please?

Having tried to add CSS to <i>title</i> without success, I’ve discovered (through fairly extensive searches) that styling actually can’t be applied to the title tag. Thanks for your help.

Hi
Rather than looking for a custom post editor, I think what you might need is a plugin that allows you to create your own custom fields. There’s quite a few; go to add new plugins from WP Admin and search “custom fields”. If you want users to provide input using the fields you’ve created, you need to use forms. There are plugins that enable creation of forms too. Once you have your fields, you’ll also be able to display specific field content by creating your own shortcodes to use in your post editor.

Hope this helps.

Thanks for responding and testing. I tracked the issue back to some deprecated PHP in a plugin (have contacted the plugin author).