netmined

Hello,

That page which is meant to be locked is not the welcome page for the website but nonetheless, at the moment the whole website gets locked.

We thought that we has set up the general settings in a way which would not restrict the whole site. Could you please let us know if there are any specific general settings which will enable us to lock one page only and how these settings should be set up?

Many thanks in advance for your reply.

Hello,

Thank you very much for getting back to us.

So just to clarify, we did only get the WP style login page but the problem was that we got this for the whole site when we only set it up for one page.

Here is a screenshot of the page set up. We have the page ID loaded and we set it to be at 0 level but as we mentioned, it locks the whole site.

https://prnt.sc/fMQRLZCBh6Um

The site is a live online store so because of this issue, we could not keep the plugin activated so currently you will not see the issue.

Here are a couple more screenshots of the general settings we did on the plugin – not sure if they will help:

https://prnt.sc/09Io6fuSvUZ2
https://prnt.sc/O0C1iZv-7SxK

Could you please advise how we can restrict the login page just to the page ID which we have loaded in the settings.

Thank you kindly in advance.

Hello,

Thank you very much for getting back to us to let us know, we will try a different plugin in that case.

Hello,

Thank you for your reply. We tried the suggestion from @askmagic and so far it seems to have worked so thank you very much.

But if you don’t mind, just in case it starts playing up in the next day or so, we will leave the topic open for now.

Thank you again.

Hi Daniyal,

Thank you so much for your quick reply and the code snippet, it fixed it! ??

Much appreciate your help.

Hello Mihaela,

Thank you very kindly for the snippet, that worked. ??

Have a great day!

Hi Mike,

Thank you for your reply, much appreciate it.

Just to clarify the situation, there were also a couple of other issues outside of Smash Balloon which were identified and which we fixed. This one was the only one left which was still getting raised by Siteground as an issue in terms of the load.

In any case, we would appreciate you taking a look to see if there’s anything we can do to fix this so we’ve submitted the ticket on the plugin forum page as you’ve requested.

Thank you again and enjoy the rest of your weekend!

Fred,

You’ll notice I used the word “if” rather than “did” so not an accusation, simply a speculation about whether the authors had done this.

The user’s location is correctly determined by wordpress & woocommerce without Swift Lite. When Swift Lite is switched on, this breaks and the user’s location is no longer correctly determined. When I ask on the plugin’s support forum about this, I am immediately told that geolocating the user correctly is a premium feature. So if the plugin’s support are aware of all this then naturally it makes me wonder whether it was a conscious decision by them to restrict the user’s location.

And if that is not the case and this is issue is some kind of bug which the plugin authors fix, then I’ll gladly be the first to apologise for any offense that my speculation may have caused.

Hi Fred,

Thank you for your reply however you have misunderstood our question.

We are not asking for geocaching – we are saying that at the moment, Swift Lite DOES not recognise the user’s location correctly and this is breaking other plugins as well as some Woocommerce features.

The problem is definitely inside Swift, not anywhere else. Other caching plugins do not have this problem, only Swift.

As we said above, the Woocommerce caching option is not the way to fix this – it causes other issues on websites.

The user’s location is recognised fine without Swift enabled so if the Swift authors have intentionally manipulated their plugin in the free Lite version so that the user’s location is not recognised, just to sell the premium version of this plugin, that is a pretty sad reflection on them and their business practices.

Hi, thank you for your reply.

We’ll try the the AJAX solution – as mentioned, the additional Woocommerce GEO IP locating button causes too many other issues.

Thanks again.

Thank you for that, we’ll rate it now.

• This reply was modified 7 years, 6 months ago by netmined.

Many thanks for your quick reply, appreciate it.

We have over a 150 individual products in our store – is there any other way to be able to enable the billing agreements for the entire store, for all products rather than having to go in manually and changing it product by product?

Thanks again.

Ok but ‘app’ property is a paypal term apparently referring to variations.

Can you please leave this query open in case someone else who knows what this is about can answer it.

Mike, it is definitely Paypal who built that plugin. They had to do it because none of the other plugins, including the Woothemes and AngelEye (which we also tried) worked for the Paypal hosted solution in Australia. Paypal’s hosted Payments Pro is different in Australia to the US so this is why none of the others would work and they had to write their own. I tried to attach a screenshot to show you but it won’t allow me paste here.

I think the culprit is somewhere in the last couple of updates because it was still fine with v.2.5.2.

I was asking if you know what would be causing “Cannot read property ‘app’ of null” in terms of changes to variations which may have been done in those upgrades. Paypal will not give more info and are saying it is a Woocommerce issue.

Hi Mike,

Thanks for the reply. It is a custom built plugin by paypal themselves. They tell me that the problem is with the updates to Woocommerce not with paypal. Since the plugin hasn’t had any updates but woocommerce has, I’m inclined to think that they’re right.

Happy for you to take a look on the back end. Let me know where to send credentials.