Slaacr

So not exactly, I have to go in a “regenerate css” all the time. Still rarely has any effects on the outcomes. What does happen, and is very suggestive of caching issues, is sometimes it will work on a fresh reload of the caches, CSS, browsers, etc. But as soon as I refresh or click off page and come back, it quits working. I have left everything installed as it is for now. I am going to move to a different server setup and see if there is something wrong with Apache settings. Maybe try Laragon. It doesn’t make sense to me that it’s not working, I’m just eager to solve this ??

Nested Container Setup
https://snipboard.io/k5FczG.jpg

Settings for Container 1
https://snipboard.io/voKFAN.jpg

Settings for Container 2
https://snipboard.io/hfsXzD.jpg

I’m now of the mind that we cannot have multiple restrictions on the same page. Container 1 restricts logged out users or certain subscription plans. Container 2 is for logged in users with allowed subscriptions. I believe the multiple restrictions are having conflicts. The reason I think this is last set of settings on the page works after caching issues are resolved. I can swap the containers places and make test user changes (or log out) and it works instead.

I’ve gone ahead and abandoned the use of this feature for now. I am going to go ahead and use elementors display conditions instead. Keep in mind, I would like to help fix this if you are interested.

Ok, I do appear to have the issue pinned down. It concerns me greatly since new “subscribers” of any plan are likely to see all the buttons until.

1. Logout
2. Regenerate Elementor Cache & CSS
3. Log back in ( if buttons still exist, refresh page ) and everything works for that user.

If I upgrade that users plan, as long as I repeat those steps it works. Harsh for testing.. Even worse if I can’t figure out how to fix caching. I wonder if other caching plugins are going to do the same?

• This reply was modified 3 weeks, 3 days ago by Slaacr.

Thanks for getting back

“testing this you should?not?test with an Administrator account or a user account that has Admin privileges”

I had read your comment about that in another thread, this is why I created a test user. The user by default was a WordPress subscriber. I manually gave this user a subscription plan. Incognito didn’t change anything in way of blocking the content.

After some contemplation last night, I had a hunch that I tested this morning. The initial solution is you cannot put the restricted content too deep in nested containers. I moved the buttons all the way out to the container that splits the body content (2nd level essentially). not ideal for this layout but I would have make made it work. Just to be thorough the 3rd level container that housed the buttons was supposed to be restricted, for efficiency, not every button individually. It did not matter whatsoever what settings you put on that container or buttons, everything showed on 3rd level container. Somehow changing the page in a significant way temporarily fixed it.

With the test user on the basic plan the right buttons showed and the higher plan button went away. Hurray! Now, If you change the subscription plan on the test user to a higher plan ALL buttons show again. Regardless of settings. I am not using a cache plugin and dumping the browser cache and incognito once again still does not fix it. I switched the test user back to the lowest plan and all buttons show.

Thanks

• This reply was modified 3 weeks, 3 days ago by Slaacr.