Gauravk

Following this thread.

Requesting IPS to delete the original images after storing the Large and Small resized images.

Technical workaround for future rebuilding images, IPS can store 1 more resize Large size image (without watermark) as a backup and discard the original ones.

The reason is these days many DSLR cameras and hi-tech phones are creating 20-40 MB images. When the system resizes to Full-HD it results in 200-500 KB max.

Storing original size images is causing huge disk space usage and daily backup consumes a lot of server power and bandwidth.

We have reached 375 GB daily backup due to these images and are restricted now to save only 2-3 days last backup instead of 7 days.

Hoping IPS realizes this issue and offers some way out in the future, please.

Let me explain with an example.

On June 5, 5:33 PM the user uploaded an image of 6.5 MB.

Here is the original (user uploaded image).

System resizes to large size and small thumbnail at the same time.

A large image (535 KB Hi-Res) is used for displaying with a watermark in a gallery and a small is used for the thumbnail.

If we manually delete the original 6.5 MB image, will the resized large (535 KB) and small (67 KB) images will be impacted or not?

Thanks Jim for adding the clarification. Please advise how can I request this change for future release?

Also if we manually delete those thousands of original big size images, existing thumbnails and resize actual images in the gallery will stay?

Just updating the solution here: That there is No Solution.

Never built user community with IPS who uploads many images, as all uploaded images using modern cameras and phones produce 10 -40 MB original images x 10,000 images have no way to be discarded.

Reason: They may be used again in the future for creating hi-res thumbnails.

Updated again

I have updated FTP details on the file, please connect to help explain why original images aren't getting deleted from the upload folder.

Each month folder is adding 3-6 GB every month.

31 minutes ago, Marc Stridgen said:

We would have to first create a fix for the issue in order to do that. Once its resolved, we would tend to get fixes out quite quickly for these kinds of things

Many thanks for your understanding.

Thank you Marc, for the quick investigation and for realizing the issue with IPS codes.

Can we please have some quick patch or workaround or some messaging to display to help over 70% of iOS users within our community, please?

Sorry, I thought that you've read Cpanel support response. My bad.

Thanks for helping with the investigation.

I'm getting the error on random pages with my iPhone with updated iOS 15 and updated safari browser.

You can use any iOS device and go to the homepage and click on the join now, back to the forum, back to the homepage and you will experience it failing too.

Sure shot: You can log in and try buying the subscription and use PayPal as an option, but it will surely fail. The majority of iOS devices are failing to pay by credit card. But I'm asking you to test with PayPal as it has another step before you actually pay. iOS users fail in both stripe and PayPal options equally.

Sure go ahead, but please make note of all enabled plugins and apps so that you can re-enable them only and not the dormant ones (disabled for a long time).

1 hour ago, Marc Stridgen said:

While I understand you said a plugin you have doesnt interfere with the service workers, you dont seem to have confirmed here that you have tested this with it disabled.

Yes, I did disable that plugin as it was the most recently developed one.

You can test it too, just make sure to enable it after testing as it has many features that our site relies on.

APP - Drives 1.0.7

and

Single Drive & Waitlist 1.3.6

1 hour ago, Marc Stridgen said:

You need to ensure you have tested this completely with all 3rd party items disabled.

Yes, I have tested with all 3rd party apps and plugin disabled twice.

If you need to re-verify, please do it from 2 AM - 4 AM (Dubai time) and make sure to re-enable all the plugins and apps you disable while testing, please.

Lately, many of our iOS users reported errors on random occasions and one of the few common patterns was at the checkout stage. They all consistently failed to load the site either at the subscription page level or while checking out irrespective of Stripe or PayPal.

We checked with one of the IPS developers who recently worked on the custom plugin for us and he confirmed that his line of codes doesn't interfere with "service workers".

We have disabled the server firewall, CP Hulk (security feature of cPanel), and even disabled Cloudflare completely to point straight to the server NS record and the problem still exists.

Then we turned to the "WORLD BEST SUPPORT" provider folks at Cpanel who have finally confirmed and identified that IPS JavaScript codes causing this issue.

Here is the full detail of the investigation and ways to replicate it by using logged-in users to checkout any subscription on any iOS device.

 
Looking further into this, we can see a similar defect report on Safari for this issue:
https://github.com/GoogleChrome/workbox/issues/1730
 

Here are the attached files for a bigger preview.

Hope to have a quick resolution or patch for this urgent incompatibility issue for over 70% of devices used within our community.

Please make this post private and ill supply the user detail

Please fix this error?

Member upgraded today from monthly (bought on 8 May 2022) to annual subscription and system showing new expiry at 21 May 2023 instead of 8 May 2023.

Has anyone using IOS on Mac or Iphone facing an issue while the checkout process?

We are using Stripe and PayPal and both gateways throw the same error for many iPhone users, but when they checkout with Windows or Android payment goes through fine.

3 minutes ago, Randy Calvert said:

In fact it just might make it slide into an even later release if the pushing gets too annoying. 🙂 

Good luck, then we will start sharing the facts with all social platforms, reviews, and IPS new customers.

Thanks, @Stuart Silvester I have been listening to this for a very very long time now.

Till we have a firm date of release, I will be pinging this daily.

On 4/15/2022 at 2:26 PM, Stuart Silvester said:

Having more than one subscription causes issues because the system is designed for only one.

Going by your own logic - Why the system isn't deleting, ignoring, killing, crushing, trashing, not seeing, not factoring, not considering - EXPIRED SUBSCRIPTION.

In IPS Binary 01010101 language, why Expired sub IS NOT EQUAL TO ZERO.

With so many synonyms and ALL caps, IPS should understand how much frustration this illogical behavior costs us dearly, every day.

We spend loads of money for user acquisition and when they try for one month and they aren't able to upgrade to annual after expiry, it makes them feel that we are trapping them in monthly billing for more money.

Some complain and most leave quietly, with tons of abandoned carts daily.

It's a real shame.

@opentype @Sonya* @Joachim Sandstrom @Makoto @Xaviours @elonegenio @bradybarrows @David.. @Myr @UncrownedGuard @OptimusBain @DawPi @ZLTRGO @Nakamura0114 @TecsenseAsh

If this matters to all of you a lot, let's ping this and several other similar threads daily.

Until it reaches IPS ears.

Our many members are complaining that while checkout the physical item for shipping, they are unable to edit their old address which they filled while joining.

Any specific reason why members have been unable to edit their billing/shipping address while the checkout process?

Any update on this bug, yet....?

It's been 2 months now.

Thanks, everyone for helping with your suggestions, really appreciate it.

My main concern was with the initial support using the blanket rule in the most critical instances without any "sane" logical approach.

On 5/2/2022 at 9:38 PM, Jordan Miller said:

You mentioned finding finding a bug that's related to our core software. Perhaps you can shed light on that please? We'd love to look into that further. 

Perhaps you can ask IPS developer to take a bit of a backward step to find the real reason under which all instances below the error message appear. It's really somewhere very close.

Clue 1: Rule out third-party plugins installed by user, logo color, css, server issue, cloudflare, hosting, firewall. All are working fine.

Clue 2: Payment methods of Stripe and PayPal, both are and were working fine and accepting payments without a glitch.

On 1/27/2022 at 5:55 PM, stoo2000 said:

The 4.6 version is a complete rewrite, so it's taking a little longer than a typical update would and needs extensive testing before it's ready for release.

Any expected date of release, I'm highly interested.

Is there any way we can use WordPress for part of our site (directory listing) and use the IPS authentication for all users?

Any ideas or experience sharing is welcome.

On 4/28/2022 at 7:08 PM, Gauravk said:

Please delete my above screengrab.

Gentle reminder