AWOL

@jon1signal, I didn’t start a ticket as that wasn’t what you said in the earlier reply, and I don’t know where to do so – I sent an email as requested. I don’t think the custom coding on my site is of the type that needs altering, as it is just a javascript file for creating external user IDs, and a plugin to filter which notifications go to which users (using their EUID). However if you think that will need changing, I will start a ticket, but OS support never mentioned doing this when I contacted them, so I’m not sure where this facility is; when I log in to the OS site and click support, a chat window opens and there is nowhere to open a ticket. So please explain how I do so.

@jon1signal,

I still have not had any direct reply to my issue, and the last update makes no reference to fixing it, so I have been patiently waiting for either another update, or at the very least a direct reply addressing my post here. I am OK using the old version, but I am concerned that it will stop working at some point as V.3.x seems to be a major update, but if it doesn’t send my push notifications it’s no use to me. I am now starting to see console errors related to the plugin so please give me (and others) some answers. I did email as you mentioned but nothing happened after that.

Thanks for the reply but I have uninstalled the plugin because I needed a quicker response from you; I have now coded something myself to achieve what I wanted. I may come back to your plugin at a later date, but I don’t want to implement this on all groups anyway, and it was not possible to select one group or some groups, as the individual checkboxes weren’t visible (that is where the error was appearing), so I’m not sure your suggested solution is one that suits. If I reinstall the plugin I will try to tick the only box visible, which I assume is a ‘Select All’ checkbox, but that is unlikely at the moment, especially as it also requires installing BP Classic, and I am trying to reduce the number of plugins on my site.

My host has found and fixed the issue – it was something to do with Immunify rules, and they disabled the problematic ones and are waiting for them to be reconfigured; the main thing is I can edit and update forms again! Thanks for your response anyway.

That’s great, thank you for the quick responses, and I will both try the option, and see what the update brings.

@heateor, yes I understand that, but how do I make your plugin use my custom default avatar (set in the WP settings) rather than mystery man?

@mbrsolution ,

Thank you, I will look at it.

Hi Damian @timersys,

Many apologies, and also thanks – after your last reply I had yet another close look at my Litespeed cache plugin settings, and it turns out that some cookies from another plugin in the exclude from cache (that I had been told to exclude by the plugin’s support) were in fact causing all pages not to be cached; this was in turn causing such slow loading which it seems were causing the issues with the popups not getting triggered properly. I should really have thought of this before posting this support thread, but as the popups had worked correctly before I wrongly thought the Display Rules were the issue. Thank you for your patient and speedy help.

@mbrsolution

OK, I see. Even though I have the [swpm_stripe_subscription_cancel_link] shortcode in use, I don’t have any way to see what happens when it is clicked – can you tell me where the code is in the plugin that handles this, so I can see if I can work something out to redirect?

Hi mbrsolution (@mbrsolution),

Yes, all my payment buttons were set up in the way documented.

And I already have that facility for members to cancel their subscriptions – I thought the link in the payment button settings was for them to visit if/when they did this, rather than being the url for the back to website link in the Checkout window.

Please let me know how (a) when a subscriber cancels their paid for subscription they are taken to my ‘sorry to see you go’ page; and (b) when a not yet subscribed user changes their mind before completing checkout and clicks the back to website link, that they will be taken back to the page they were on i.e. what can I put in the payment button settings to achieve this, or is that not possible?

Hi Damian @timersys,

OK I have done that and tested it myself first, with the user is logged both True and not, and what I have discovered is that once the page finishes loading, the first click on the button I set up with the spu-open-xxxx class never triggers the popup, but either a second or third click does trigger it, so this appears to be a different problem than I first thought. In my previous discovery I only ever clicked once, so probably the popups in question would have opened with a second or third click, but obviously this is still an issue that needs resolving. You can test it at https://sentlive.com/popup-test-page/ where it is set for logged out users. In case it is important I have tried that page on Firefox for Mac, Safari on iPhone and Firefox on Android, and it is the same on all of them.

Hi Damian @timersys,

I have now removed all the problem rules as it was having a detrimental effect on whether users could see popups or not, so I don’t have an ID for you I’m afraid. The site doesn’t have any firewalls, and I have been working on it all day with absolutely no connection issues, both logged in and logged out, and I have been regularly using Lighthouse to find issues all day. I just did an ‘is it down’ check as well, and it is up there too. But perhaps your attempt coincided with me working on the home page, as I am attempting to trawl through the site fixing anything that is causing speed issues, which is how I discovered the Display Rules problem – I have several Forminator forms inside popups, and these forms were appearing in the console Network tab as slow queries on pages that they shouldn’t have been appearing on. All I can tell you is what I have already mentioned in my original post about those rules not working on my site – I have had to resort to listing individually every page each popup shouldn’t appear on. In case it helps, I am using a child theme of Blocksy, latest WP, and many plugins, but previously these rules worked as far as I am aware, but I don’t know when they stopped working. It is impossible to find out now.

Hi @pavanpatil1 ,

Just wanted to note that despite an update since your reply, this is still showing up in Query Monitor, so if you did fix it in the update, it didn’t work.

I am also getting this exact same issue; the error log has reached over 6 MB in about 9 hours. I thought there might be a permissions problem, but changing them made no difference. What is strange is that there is no actual error shown in the logs, just the file location as wowsa has shown above. The locations are all the folders in the assets/blocks folder. I have everything as up to date as it can be, using the Blocksy (child) theme, php 8.1, and a lot of other plugins but until the latest update everything was fine. No obvious impact on the front end that I can see yet.

I have managed to finally resolve this, although it does leave me with some questions. I inspected the site and the clone using Chrome DevTools, specifically the Application section, and firstly discovered that the browsers were not finding the manifest on the main site, and after some research found a suggestion to create a new manifest called site.webmanifest with the relevant info from the pwa-manifest.json. This has fixed the problem, but now makes me wonder why the plugin generated manifest file was not being detected (it was detected in the clone site), so any suggestions about this would be welcome. This has also fixed the issue with the Add To Home On Element Click.

One other minor note is that I noticed that the pwa-manifest.json has all the ‘/’ characters escaped with ‘\’ which, according to a search I did on this, is not required in json files; the only text that needs to be escaped is ‘</’ according to what I read. I have not delved into the plugin files to find out if this is by design but I have to assume it is as the clone site is the same. Essemtially what I am saying is that you can get rid of the code that does this if you wanted to.