holospirit

wow – that was fast! really thanks a lot ??

message was only in live as admin. i’m not bothered by it – it’s just because because the code is behind the </html> tag – maybe due to other plugins.

Wrong Support Thread. Sorry

Dear @symptote ,

thanks for this option! i think it’s urgently needed and requested (even for pro).

i hope you release an update soon. thanks in advance.

best,
thomas

Thanks for your reply. The problem for me is, that if using the “normal” plugin, all RAW editor settings are overwritten.

hi stefan,
danke für die schnelle rückmeldung.
habe die .js direkt eingebunden ?? – dein vorschlag würde es aber auch l?sen.
viele grü?e,
thomas

ps. w?re cool, wenn du irgendwann mal zeit findest, auch an ajax zu denken, damit dan auch der aufruf mitgez?hlt wird.

• This reply was modified 6 years, 6 months ago by holospirit.

Wer etwas experimentierfreudig ist, kann die inc/class-statify-frontend.php durch diese hier ersetzen, dann müsste der Fehler weg sein.
https://github.com/pluginkollektiv/statify/blob/hf-filterInputVar/inc/class-statify-frontend.php

Sobald das Fix best?tigt ist, geht zeitnah ein Update raus.

geht, 1000 dank <3

(von status 500 auf 204)

• This reply was modified 6 years, 6 months ago by holospirit.

mayme a add_filter() or so would be a great solution?

i have the same problem (the 3 dots fadeout). the save admin-ajax call returns “0” and a 400 POST status for action: mbh_save_bounce_settings

also i get DataTables warning: table id=bounce-log – Ajax error. For more information about this error, please see https://datatables.net/tn/7 — same 400 error as mentioned above

• This reply was modified 6 years, 7 months ago by holospirit.
• This reply was modified 6 years, 7 months ago by holospirit.

good point. i solve the judge by simply using my own ajax in frontend now.

regarding the more important point of “admin filter” and cron – broker link remover, snap social auto post, updraft backup and as good every plugin with cron relevance and the applied filter isn’t executed/called. don’t ask my why – but after setting these plugins to normal execution, all is fine.

for my needs a simple is_admin() judge is ok. i think for most queries regarding ajax/json the logged in judge isn’t necessairy.

what i just found out is, that the judge in your settings “admin filter” doesn’t execute by cron calls – so every admin plugin isn’t called by cron anymore! so it must be “normal” loaded – what is quite sad.
maybe have a hint or plan to fix that?

thanks for your replay.
that was my first idea also. your regex is matching that. the problem for my “idea” is, that i e.g. need a plugin in admin area AND on selected frontend parts. so in practice i only need 2 plugins on frontend when using admin-ajax and skip the rest. but these plugins shoudn’t been deaktivated in backend itself**. right now i can only decide full/admin/page. so for my simple needs of full page speed optimisation i would like to have more options to select that. a simple json/ajax extra option with backend/frontend would give the ability to really speedup things in wp, as your plugin is really a solution for one of the worst problems in wp.

what do you think?

**or isn’t a cron call of the plugin affected by the deaktivation?

Hi @ahmedkaludi,

thanks for your help ??

for me it looks like there is a problem with PAGES. Posts, Archives and so work.

look at
works: https://holospirit.is/amp?cache=no
works: https://holospirit.is/blog/amp?cache=no
doesn’t work: https://holospirit.is/5-punkte-technik/amp?cache=no (404)
doesn’t work: https://holospirit.is/portrait/amp?cache=no (redirect to https://holospirit.is/portrait)

all the best,
thomas

i don’t know if its related with w3tc. i have the same problem. something seems to be broken: amp redirects to normal pages

• This reply was modified 7 years ago by holospirit.

thanks!

thanks a lot!