Matt Scheidler

Same problem here. My “your site is experiencing a technical issue” email came at 4am today and included this:

An error of type E_ERROR was caused in line 232 of the file /home/irss3rdf/public_html/wp-content/plugins/master-slider/admin/includes/msp-admin-functions.php. Error message: Uncaught TypeError: Unsupported operand types: string / int in /home/irss3rdf/public_html/wp-content/plugins/master-slider/admin/includes/msp-admin-functions.php:232
Stack trace:
#0 /home/irss3rdf/public_html/wp-content/plugins/master-slider/admin/views/slider-panel/index.php(200): msp_get_pro_users_num()
#1 /home/irss3rdf/public_html/wp-content/plugins/master-slider/admin/views/index.php(46): include('/home/irss3rdf/p...')
#2 /home/irss3rdf/public_html/wp-content/plugins/master-slider/admin/class-master-slider-admin.php(223): include_once('/home/irss3rdf/p...')
#3 /home/irss3rdf/public_html/wp-includes/class-wp-hook.php(310): Master_Slider_Admin->display_master_slider_panel_page('')
#4 /home/irss3rdf/public_html/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters('', Array)
#5 /home/irss3rdf/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#6 /home/irss3rdf/public_html/wp-admin/admin.php(259): do_action('toplevel_page_m...')

That documentation explains how to use placeholders for subscription links for single events, but not subscription links to the full calendar (all events.)

My client provided an example of another site that has the functionality they were seeking, using another WordPress plugin. (This plugin is worlds ahead of that plugin overall…I’ve used it before.) It offered specific subscribe links. Using that site as a guide, I came up with these links that seem to work exactly as the client was seeking:

https://calendar.google.com/calendar/u/0/r?cid=https://yourwpsite.com/events.ics

webcal://yourwpsite.com/events.ics

The webcal is self-explanatory, but the example site allowed me to determine the Google structure.

Just commenting back to this month-old thread to confirm I figured out my solution, and maybe this will help someone else.

I wish I had more specific details. When I first opened this ticket it seemed to be happening with a greater frequency. I have changed hosts and it isn’t happening nearly as often now, maybe once every 10 to 15 times a plugin is updated. Some sites experience the issue more often than others, but there really doesn’t seem to be a pattern. I’ve been keeping track of all duplicate notifications for a few weeks. If you’re not getting reports from others, I suppose it is something on my end. For now, getting duplicates every once in a while is not that big of a deal. Thank you for your time.

I appreciate the reply. I’ve been trying to keep track of when this happens, and to this point there doesn’t seem to be any discernable pattern.

While it does only happen for an automatic update, and never when I update a plugin manually, it isn’t happening for all automatic updates. When I first opened the ticket it seemed to be happening nearly all the time, but as I’ve monitored over the past few weeks it does seem to be more sporadic.

When this does happen, the second notification appears around a minute after the first. I don’t know if that is helpful information or not.

This isn’t that big of a deal, I just wanted to point it out in the event there was something that could be adjusted. I can live with the duplicates, especially since they aren’t happening every time. I do appreciate the plugin, and your time for looking into this.

Kuba, thank you for the reply. This issue is not happening on every site, nor does it happen every time. But when it does occur, it is always an automatic update via WordPress. If I update a plugin manually, only one notification is sent. Glad to provide more information if it would be helpful. Thanks!

Robert, thank you for the update. I was afraid of this. But I guess we’ll just stick with the workaround I’ve employed, for the remaining life of this website. If this is the only issue I have with a plugin I first installed 9 years ago I’m not complaining!

Robert, I ended up applying a workaround since I don’t know if this issue will be fixed.

What I did was create an event that occurs on the 5th Thursday. Then I created second event for the 4th Thursday, with exclusions for the months in which there are 5 Thursdays. A bit of extra work, but I do have the proper dates showing on the calendar. I’ll have to remember to add exclusions for future years, but I’m hoping this does get resolved before that becomes an issue.

I have a client reporting the same issue. The form output runs together in a single paragraph. I tried un-checking the HTML box but that did not make any difference. Are any other potential workarounds available until the plugin can be updated to correct this?

performo, thank you.

I just upgraded from 5.12.1 to 6.1.1 and everything was just as you’d described. I made the change on line 2234 and that did restore the prev/next functionality.

If anyone else needs to do the same thing, here’s a copy/paste ready version of the code.

const calendar_id = calendar.closest('div').attr('id').replace('em-view-','');

Looking forward to this being resolved in the plugin itself.

I gave it 12 days, but just now reverted back to 5.12.1 in order to restore the previous/next buttons for my calendar. Looking forward to a 6.x update.

Humayon,

Thank you for the reply. I’d tried a couple of capability plugins first before opening this thread. For now I’m just going to allow delete_posts while continuing to restrict delete_pages. Keeping editors from inadvertantly deleting pages is my primary concern; I’ll just have to open up the possibility of inadvertent deletion of posts from other custom post types, which is somewhat unlikely.

Thank you for the prompt support and for a great plugin.

Mikko,

Thank you very much for the prompt and accurate response. I have rebuilt the index and everything seems to be back to normal.

I truly appreciate the quick reply. Keep up the great work!

My only thought is either Jetpack or a security plugin.

The Log entries in question all look like this:

Key	Value
id	72
logger	SimpleUserLogger
level	info
date	2022-01-18 15:07:44
message	Logged out
initiator	other
context_message_key	user_logged_out
_message_key	user_logged_out
_server_remote_addr	**.**.***.0

They are typically coming from one of two IPs.

This compares to my own Logout log entry which includes an initiator of ‘wp_user’ and values for my ‘_user_id’, ‘_user_login’, and ‘_user_email’.

As long as I know that the logout doesn’t correspond to a unwelcome login it’s not a huge problem. Thank you for your reply.

Versions 4.1.6 and 4.1.7 do hide the black toolbar but there is a way to turn it back on. Go to the new Settings screen and the first option is “Adjust for WP Admin Bar”. For some reason this is set to “None” by default, but if you change it to “Adjust” the black bar is restored.

The default probably should be the other way around, considering it is changing something that we didn’t have a setting to configure in the first place. But at least there’s an option to fix it.

Sweta, thank you for the reply. I was able to accomplish what I was seeking. Thank you for pointing me in the right direction!