You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the format/syntax of the pmpro_lpv_count cookies?
As there seems to be an issue when admin change the limit (or add membership level) and i believe the cookies on those user's PC (who was already viewing the posts in the website before the admin made a change) is not really updated?
The website posts' limit is now inconsistent.
The text was updated successfully, but these errors were encountered:
We need to come up with something better. As @fransverztec points out, if the settings change it may become incompatible with the cookie string.
There are other issues. The current PHP implementation to redirect away when the limit is reached seems to assume the period is months, although now in the settings you can set days or hours. Expiring the cookie like we do may not always track views in the way expected.
We'd also want to support MMPU, cases where a user has more than one level. Instead of setting their views based on the first level for them, we want to use whichever level has the most views.
We should consider using JSON to encode the cookie string instead of a parsing out via commas and semicolons like this. It would be easier to get more data into the string that way.
What is the format/syntax of the pmpro_lpv_count cookies?
As there seems to be an issue when admin change the limit (or add membership level) and i believe the cookies on those user's PC (who was already viewing the posts in the website before the admin made a change) is not really updated?
The website posts' limit is now inconsistent.
The text was updated successfully, but these errors were encountered: