MyLiveChat – Free Live Chat & AI Chatbot

2.1.7

• When the check confirms the chat code is live, the screen now says what has to happen next: sign in to the agent console, because the chat button is on your site but nobody is behind it until someone does, and then start a chat with yourself from your own site. Chats that arrive with nobody signed in become offline messages with the visitor’s email address, and the screen says so rather than leaving it to be discovered.
• The settings screen now checks whether the chat code is really on your site instead of only saying that a Site ID is stored. It loads your front page the way a visitor would and looks for the code; if it is missing you get the three things that actually cause it — a cache serving a page from before you saved the ID, a “delay JavaScript” rule eating the script, or a theme that never calls wp_footer() — and a button to check again. If the check itself cannot reach your site, which is common on hosts that block such requests, it says so rather than claiming the widget is missing.
• The plugin asks, once, whether you would leave a review on WordPress.org. It appears only for administrators, only on the MyLiveChat screens and the Plugins list, only when a Site ID has been saved and working for 30 days, and never while the email-confirmation notice is still up. Answering it in any way — including “No thanks” — ends it for good; there is no reminder that comes back. Ratings are how the plugin directory decides what to show people, and nothing in the plugin had ever asked.
• Records when the Site ID was first saved, which is what that 30-day wait is measured from. Deleting the plugin removes it, along with the answer to the review question.

2.1.6

• Listing only, no code change: renamed to “MyLiveChat – Free Live Chat & AI Chatbot”, and the tags now read live chat, livechat, free live chat, chat, chatbot. The old name spent twenty characters on “Plugin for WordPress”, which nothing in the plugin directory searches for, and the AI assistant the plugin has shipped for some time was not named anywhere a merchant would look.

2.1.5

• Fixes a fatal error that made the plugin unusable on PHP 8. Version 2.1.4 registered the email-confirmation reminder against admin_notices but never shipped the method it pointed at; the 2.1.4 rewrite of the settings screen removed the method and left the registration behind. 2.1.2 and 2.1.3 are not affected — both were checked on PHP 8.2 and neither raises the error. On PHP 7 an invalid callback was only a warning, so the reminder simply never appeared; on PHP 8 it raises a TypeError, and because admin_notices runs on every admin page the whole WordPress dashboard showed “There has been a critical error on this website”. If you installed the plugin and your admin went blank, this was why — updating fixes it, and nothing on your site or your MyLiveChat account was affected.
• The reminder described in 2.1.3 works again: administrators see it on admin pages until the account email is confirmed, and it can be dismissed.

2.1.4

• The settings screen is now fully translatable. Every visible string goes through the text domain and a languages/my-live-chat-for-wp.pot template ships with the plugin, so it can be localised the way the chat widget already is.
• Removed the inline onclick attributes and the inline script that fixed up the two dropdowns after the page rendered. The selected option is now marked server-side, so there is no flash of the wrong value and the screen works under a Content Security Policy that disallows inline script.
• Accessibility: the settings table used td scope=”row” for its row headers, where scope has no effect. They are th scope=”row” now, so screen readers announce the label with each field.

2.1.3

• New accounts created from the settings screen are inactive until the emailed link is clicked, but the chat widget goes live immediately — so visitors could start chats that nobody was able to answer, with only a one-line hint on a screen the admin had already left. A reminder now appears on every admin page until the email is confirmed, explaining what is and is not working and how to get a fresh link. It is dismissible, and only administrators see it.

2.1.2

• Fixed: MyLiveChatAdmin shared its singleton storage with its parent class, so whichever ran first decided the type both returned. Any request that touched the admin and front-end paths together could get the wrong object back.
• Added a “Settings” link to the plugin’s row on the Plugins screen. The previous attempt was registered against the global plugin_action_links filter, which would have added the link to every other plugin’s row, and had been left disabled; it now uses the per-plugin hook.
• Added uninstall cleanup, so deleting the plugin removes its six options instead of leaving them in the database forever. Multisite deletes are handled per site.
• Fixed: the MYLIVECHAT_VERSION constant still said 2.1.1 while the plugin header said 2.1.2. It is used to bust the cache on the admin CSS and JavaScript, so an upgrade could leave stale assets loaded.
• Output escaping is now applied at every point of use rather than when the value is assigned, so the escaping is visible where the output happens.
• Added the missing text domain to a translatable string, and a guard around a superglobal index read.
• Documented why the two request reads on the settings screen need no nonce: they only choose which confirmation notice to display.
• The plugin header name now matches the name in readme.txt, so the two can no longer drift.