ivantrendafilov
Forum Replies Created
-
Forum: Plugins
In reply to: [TablePress - Tables in WordPress made easy] Strange permissions issueBut the person has the Editor role and the tablepress_edit_tables capability. Indeed, TP shows them as the author of the table.
Forum: Plugins
In reply to: [TablePress - Tables in WordPress made easy] Strange permissions issueHey Tobias,
So, the stack trace is added by the plugin Query Monitor. The default error message indeed says “Sorry, you are not allowed to access this page.”
Forum: Plugins
In reply to: [Yoast SEO] Using Readability Eye Icon breaks Classic EditorAnd the thread is bizarrely marked as “Resolved”, even though the bug remains.
Hey Tobias! Thank you for the quick response and apologies for not clarifying. I am referring to the “Table Information” section on the “Edit” screen.
Forum: Plugins
In reply to: [Yoast SEO] Using Readability Eye Icon breaks Classic EditorDid someone actually create a github issue for this bug?
- This reply was modified 1 year, 10 months ago by ivantrendafilov.
Forum: Plugins
In reply to: [Yoast SEO] Using Readability Eye Icon breaks Classic EditorThe exact same thing happens on a brand new site with the latest Yoast SEO plugin and Classic Editor installed. There are no other plugins installed on the site and you can clearly see the bug in the video:
https://www.dropbox.com/s/yznllgdxx46ey2m/screen-recording-2023-01-17-at-142151_zDmWoxay.mov?dl=0
Forum: Plugins
In reply to: [Yoast SEO] Using Readability Eye Icon breaks Classic EditorYes, the bug exists even if Yoast is the only plugin and it’s on the default theme. Please look into it.
Forum: Plugins
In reply to: [TablePress - Tables in WordPress made easy] Cannot save with 2.0.2Do you think removing the plugin and rolling back to 1.9.5 would be safe? Nothing will break on tables created with the 2.x version?
Forum: Plugins
In reply to: [TablePress - Tables in WordPress made easy] Cannot save with 2.0.2Hi Tobias — I have the same issue on 2.0.3. It works through an Admin account, but it does not work through an Editor account. We use a Roles plugin and have assigned all permissions to the Editor role, yet the tables cannot be saved and this JS error shows up in the console:
Uncaught TypeError: Cannot set properties of null (setting ‘disabled’)
at tp.helpers.options.check_dependencies (edit.js?ver=b575992d3efd457d3f41:1:2332)
at tp.helpers.options.load (edit.js?ver=b575992d3efd457d3f41:1:1419)
at edit.js?ver=b575992d3efd457d3f41:1:34408
at edit.js?ver=b575992d3efd457d3f41:1:38056- This reply was modified 1 year, 10 months ago by ivantrendafilov.
- This reply was modified 1 year, 10 months ago by ivantrendafilov.
Thanks, amazing improvement and congrats on the 2.0!
Okay, thanks for the response.
no
Forum: Plugins
In reply to: [LiteSpeed Cache] Image Optimization stuckIt appears to work now. Thanks!
Forum: Plugins
In reply to: [Super Page Cache] Cache and geolocated contentIs it possible to add a hook into the “related pages” purge code, so that I can execute my own logic on what is considered a related page?
Generally, for my use case, I’ll have 10k pages, cached 50 x 10k times (each page’s content varies depending on the US state of the visitor), so just to preload all of these into the CF cache is going to be difficult, if I have to purge everything on each update, then it’s not going be sustainable at all. On the other hand, if I can hook into that code and purge the cache keys that are basically URL + query param for each US state, then it becomes very reasonable and effective.
I would imagine it would be useful for other people as well, if they end up modifying your default worker to include new params (e.g., like in that device detection gist example).
Forum: Plugins
In reply to: [Super Page Cache] Cache and geolocated contentHello,
First off, thank you for your response — it is very helpful.
> But if you look at the code you will see how we are creating different cacheKey by attending a query string to the URL inside the worker which the user can’t see but to CF it will be treated as a different cacheKey
That is a clever idea, I can just edit the worker to attach the
request.cf
headers I need as query strings, which will create unique cache keys for each location of interest. But this brings up another question — how does cache invalidation work? I.e., imagine some page is currently cached, but someone goes in and makes an update. Will the plugin be able to purge each individual cache key, varied on all the geolocations, for that page? Or does it simply wait X amount of time for the cache to automatically expire? Or does it do a purge all?Re: the somewhat counterintuitive idea of using CF geolocation headers instead of some API: better performance on a cache miss than any API and also allows us to serve the bulk of the requests from a geo-split html cache on LiteSpeed, instead of doing server-side PHP execution.
- This reply was modified 2 years, 8 months ago by ivantrendafilov.