adeelkhan

Apologies for the delayed response. Let me clarify the scenario.

When the ‘Cache Logged-in Users’ option is enabled in Breeze, it creates caches based on user roles, as mentioned earlier. However, it also generates separate caches for each user session.

To elaborate, if you log in with the customer role as ‘first-customer,’ Breeze will create a cache specific to ‘first-customer’ with its unique user ID. Similarly, when you log in as ‘second-customer,’ a separate cache is created for ‘second-customer’ with its distinct user ID.

You mentioned the possibility of applying a functionality where all logged-in users with the same role share the same cache file. However, this approach may pose issues as it lacks the separation of identity for each user, potentially causing problems.

Thank you for reaching out. We appreciate your concerns and are actively investigating the points you’ve raised.

In order to expedite the resolution process, could you please provide specific details or steps that would allow us to replicate the issue from the user’s end?

Kindly provide your Breeze configuration settings.

Additionally, could you confirm whether multiple JS files are rendered simultaneously during page loading?

Allow me to explain the functionality of purging the cache. Essentially, when you initiate a cache purge, it is done to fetch updated content. During this process, all relevant cache for that particular instance is cleared. For example, when you update a post, not only does the cache for that specific post get purged, but also the cache for all the categories associated with that post.

Clicking on ‘Purge All Cache’ removes the entire cache and recreates it from scratch. These actions are executed with just one click, and they happen almost instantly. The suggestion you provided may not be suitable for these conditions because when a user performs the ‘Purge Cache’ option, it doesn’t clear all the cache. Using the preload feature to create the entire cache might lead to redundancy, which is not ideal, in my opinion.

First and foremost, I want to extend my sincere apologies for any inconvenience you may have experienced.

Your feedback is invaluable to us, and it plays a crucial role in our continuous efforts to enhance our product. We greatly appreciate the insights you’ve shared, as they contribute significantly to our ongoing improvements.

In order to better understand your suggestions regarding the optimization of the multisite feature, we would be grateful if you could provide additional details. Your specific insights will help us tailor our efforts and address any issues more effectively.

Additionally, concerning your mention of displaying notices to unauthorized users, providing specific scenarios would be immensely beneficial. This would enable us to grasp the situation more comprehensively and make the necessary adjustments to ensure clarity and appropriateness.

We truly value your input and are committed to making the necessary enhancements based on your feedback. Thank you for taking the time to assist us in improving our product.

Could you please provide more details on your request to purge the cache? Specifically, we would like clarification on whether you want to purge the cache not only in the general context but also specifically for Custom Post Types (CPT), tags, and taxonomies. Your elaboration on this matter would be greatly appreciated.

Thank you for sharing the details. We appreciate your input, and we will certainly look into it and provide a solution. I have forwarded it to our development team for further investigation.

We value your use of our plugin and welcome any feedback you may have. If you encounter any further confusion, please feel free to ask. Thank you again for choosing our services.

Thank you for reaching out to us regarding the issue you’ve been experiencing with our plugin. We want to assure you that we are fully aware of the conflict that arises when our plugin is used alongside another specific plugin, due to differing versions of a shared library.

Our development team is actively working on a solution to this problem. We understand the importance of ensuring compatibility and are committed to resolving this as efficiently as possible. Our approach involves isolating our version of the library to prevent any interference with other plugins you may be using.

While we are working diligently on this, we do not have an immediate fix at this moment. We appreciate your patience and understanding as we navigate through this technical challenge. Our goal is to ensure that our plugin operates seamlessly within your environment, and we are making every effort to achieve this.

We will keep you updated on our progress and will notify you as soon as a solution has been implemented. If you have any further questions or concerns in the meantime, please do not hesitate to contact us.
Thank you for your continued support.

Thanks for sharing the details. We are currently investigating the point of conflict and will share our findings once the investigation is complete.

Thank you for providing the details.

Could you please share the structure of your CRON job request?

Please insert the following code into the child theme’s functions.php:

add_filter(‘breeze_custom_headers_allow’, function($custom_headers){ return array(); });

After adding the code, navigate to the Breeze plugin and save settings on the ‘Basic’ tab to reset the breeze-config.php file.

Thank you!

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

Could you please provide more details on your request to purge the cache? Specifically, we would like clarification on whether you want to purge the cache not only in the general context but also specifically for Custom Post Types (CPT), tags, and taxonomies. Your elaboration on this matter would be greatly appreciated.

I presume that the mentioned issue has been resolved since you indicated the status as ‘resolved.’ Kindly confirm this for clarity. If, however, the problem persists, please provide detailed replication steps so that we can thoroughly investigate and address it.

To facilitate this process, it would be immensely helpful if you could provide us with the code snippet that should be added to the .htaccess file.

I would like to bring to your attention the release of the latest build, Breeze version 2.1.3.
This update includes a significant improvement in the system’s functionality, specifically addressing cases where no “HTTP_USER_AGENT” header is sent. The enhancement ensures a more robust and seamless experience for users in various scenarios.
To benefit from these improvements, kindly update to Breeze version 2.1.3 at your earliest convenience.