adeelkhan

If the page is still serving from the cache, have you checked for any other caching systems installed on your application or server?

After delete the Breeze plugin, the cache will no longer be served by Breeze.

We advise against using plugins that duplicate Breeze’s functionality, as it may lead to conflicts and user issues.

Could you please clarify the specific functionality you intend to use with another plugin alongside Breeze?

Thank you for sharing your insights! I appreciate your input. I’m curious to learn more about your experience with CSS and JS minification using the Breeze plugin. If you could share your thoughts or any tips, it would be highly valuable. Looking forward to hearing from you!

As mentioned, encountering a 508 error during the installation of a new WordPress site suggests that some requests or actions on that page may have led to resource exhaustion. To verify this, please navigate to the Reading Settings section and select a static page as the Homepage. After making this adjustment, check the response to see if the 508 error persists. This will help us further investigate and address any potential resource-related issues. Your cooperation in resolving this matter is greatly appreciated.

Thank you for providing the details. Your cooperation is highly appreciated. For a more comprehensive investigation, we kindly request you to reach out to our support team and create a ticket. We will thoroughly examine the point of conflict and promptly share our findings with you and our user community. Thank you for your understanding and assistance.

• This reply was modified 1 year, 1 month ago by adeelkhan.

The error 508 ‘Resource Limit is Reached’ occurs when your resources have been exhausted.
Secondly, regarding the point you mentioned about cached content, it’s quite possible that it’s served from your browser cache. Please verify this by checking on a different browser.

We sincerely apologize for any inconvenience you may have experienced. Could you please take a moment to share the issues you are facing while using Breeze? We are committed to resolving any challenges our users encounter and would love the opportunity to address and fix any issues you’re currently experiencing with Breeze.

The issue has been resolved in version 2.1.4. Kindly update the plugin.

Thank you for your response.

Could you kindly verify the following: disable the entire JavaScript minification and observe if the JavaScript code reflects in your browser as expected? I am exploring the possibility that the inline JavaScript of Breeze may be minifying existing code in the web browser, leading to an increase in file size. I hope my point is clear.

Your confirmation would be appreciated.

It seems like you want to disable lazy loading for certain images by applying the “no-lay” class only to those specific images. The rest of the images will still be served using lazy loading. Is that the clarification you’re seeking? please confirm

Thank you for sharing the details regarding the reported concern. Allow me to provide a more detailed explanation of the functionality of the “Include Inline JS” option in Breeze.

The primary purpose of this option is to minify JavaScript lines of code that are rendered on your web application. It’s important to note that the option does not create its own JS script; instead, it works by minifying existing inline scripts and adding them to the JS minification file. This process may result in an increase in the file size due to the inclusion of minified scripts.

In response to the point you mentioned about the random rendering of JS code on your web application, the Breeze option “Include Inline JS” is designed to address this by minifying and consolidating those scripts into the JS minification file.

For further confirmation and to isolate the cause of the file size increase, I recommend temporarily disabling the entire JS minification option. After disabling it, please check your web application page to confirm whether the JS code is added there without minification.

Your cooperation in performing this check will greatly assist us in pinpointing the issue accurately. If you have any questions or require further clarification, please feel free to reach out.

Thank you for your understanding and collaboration in resolving this matter.

Okay, no problem. It becomes a bit challenging to sort it out.

Nevertheless, once you initiate the cache purge from Breeze, all the minified JS files are removed, and a new one is generated. Over time, it seems the size of the same JS file increases, right?

Could you please confirm the following as well? When you visit your site, a JS minified file is created under the ‘/wp-content/cache/breeze-minification/js/’ folder with a name like ‘breeze_1ac7ab179399dbe3f85d0d062a827178.js.’ According to your description, the file size increases after 1 minute without applying any changes in the Breeze settings.

If this understanding is accurate, could you kindly verify the changes that have been incorporated into the JS file causing the size to increase?

I appreciate your assistance in clarifying this matter.

• This reply was modified 1 year, 1 month ago by adeelkhan.

Don’t worry. Please follow these steps to identify the point of conflict:

1. Enable debug.log and check the log file while applying the following steps.
2. Deactivate all plugins except Breeze and check if the issue still occurs. If it does, proceed to the next steps.
3. Apply the default WordPress theme and check if the issue persists.
4. Additionally, inspect the console errors in the browser’s developer tools for any insights.

Thank you for the update, and it’s great to hear that you’ve identified the point of conflict, which is related to authentication and not associated with Breeze.

Please feel free to reach out to us whenever you encounter any conflicts with Breeze functionality. We are always here to help and resolve any issues our users may face.

In the minification folder, Breeze compiles all JS and CSS files rendered in the application into their minified versions. As you mentioned, there seems to be uncertainty in the behavior of Breeze creating a minified JS file that increases in size. Whenever a page is visited, Breeze minifies all JS files and places them in the minification folder, serving them from there.

If you could please contact our support and create a ticket, we will thoroughly investigate the point of conflict and ensure to share our findings with our users. Your cooperation is much appreciated.