Af777 swivel attachment near me.Makakuha ng libreng 700pho sa bawat deposito

David Bee
(@davidbawiec)

1 year, 7 months ago

Hi! Back here with a bug report.

In the latest version of Breeze, under the Advanced settings tab, we have the ability to specify query string parameters under the “Cache Query Strings” section. Urls that include any of the parameters should be cached. Your KB article about this further clarifies this:

If multiple parameters in a URL with at least one of your defined parameters is present, the page will be cached.

However, this doesn’t seem to be the case. On line 158 in the execute-cache.php file, the code checks if 0 !== (int) $breeze_query_vars_list['extra_query_no']and if so, does not cache the page. Let me explain:

Using the example from the KB article, let’s say my page URL is https://example.com/page/?country=germany&eyes=blue, and I define country as the query variable that Breeze should look for and always cache pages that include it. However, the method check_query_var_group() in Breeze_Query_Strings_Rules will only see “country” as a recognized query var, and place “eyes” in this case in the extra_query_no count. Which would lead to the URL not getting cached at all. Which means the code isn’t really working as intended. It sounds like the code should unset all elements from $not_found_anywhere if at least one of them was found in $user_defined_query_vars.

I can see the necessity to sometimes specify all the query parameters before caching a URL. But it would be great if we could in fact also have some sort of wildcard version where if ANY of the parameters are present in the always cache list, cache the entire URL (as per the original intended usage and the KB article).

Thoughts?
David

The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)

Plugin Author adeelkhan
(@adeelkhan)

1 year, 7 months ago

You have discussed two points first Cache Query Strings and second Never Cache URL(s)

while add any URL in Never Cache URL(s) there is no-cache header add in define URL and its by pass from cache.

while add query string single or multiple in Cache Query Strings it served by cache

like you have entered
https://example.com/page/?country=germany&eyes=blue — its served by cache
https://example.com/page/?country=germany&eyes=blue&test=one — its not served because test not define in Cache Query Strings but no-cache header not include until place the same URL in Never Cache URL(s)
Thread Starter David Bee
(@davidbawiec)

1 year, 7 months ago
Hi @adeelkhan

Thanks for your reply. Yes, I understand that adding a URL to Never Cache URL(s) will mean that the URL will never be served from cache. So I did not add https://example.com/page/ (or any variation of it) to that list.

However, according to the Knowledge Base document, if I add country to Cache Query Strings, any url that includes “country” should be served by cache. So all of the following variations should be served by cache:
Please test, and you will discover that this does not happen. Only the first URL gets served by cache. This is incorrect behavior, as all three of the above URLs should be served by cache. I explained in the original post why this is happening and how to fix it. Let me know how I can help support you.

Thanks!
Plugin Author adeelkhan
(@adeelkhan)

1 year, 7 months ago

Thanks for your explanation. Actually in KB we define that how to use the option. Basically the option Cache Query Strings served entire URL on the basis of strings define in it.
We may also explain the points in KB also to provide better understanding the option.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Bug Report’ is closed to new replies.