jnz31

totally agree. whack move to put their spam bs on the dashboard / health-monitor.

@dfactory no, its not. your plugin does create a critical issue. and @ainlinaprops is not writing about any force. i must say i do agree, these messages tend to raise panic and i’ll call it what it is: spam

huh?!
yes, yes, yes, latest of the latest version running.. everything and all is latest, just double-checked aka. 2022.1.0..

hi @threadi
well, no. you seem to not understand the underlaying issue here.
usually, when loading a page/post and you use some sort of extra styling via gutenberg, these styles will be processed and attached on page load.

but consider switching url and loading your stuff via rest api. then you get the contents, like title, content, featured image, etc. but the styling is missing. this has nothing to do with the request nor theme..

for now i am using this solution.

• This reply was modified 2 years, 7 months ago by jnz31.
• This reply was modified 2 years, 7 months ago by jnz31.

haha, dont be so hard on yourself ??
looks like it is working now. thanks!!

jaman, that totally helps and works! thanks. wicked, as it makes it super easy to query for multiple attributes!! ??

hi @sebd86
thanks for the fast reply.
1. i modified the other ticket too often and it is now blocked for revision.

2. yes, the url should be fine, attribute is called finish and the slug (i copied it from the url of the taxonomy term) is pa_finish, the id exists as well..

3. if i modify the url to only ?attribute=pa_finish or ?attribute_term=xxx its the same result

• This reply was modified 2 years, 11 months ago by jnz31.

in 3.0.1 the issue is solved. thanks for the update.

hi jarnovos, thanks for the quick reply. that definitely helps. keep it up..

LOL. i didn’t even realize i fixed this bug before ?? with explanation and all. it probably reoccurred since i installed some updates.

+1
solution provided on github removes the warning.

happy new year everyone!
this problem still persists.
can we get an info about update on this once again?

ciao @tneville, thanks for getting back

i see. strange.
i did that test now, status closed, service non. connected the email in my email client for testing with no issues whatsoever. still weird..

so for reproduction purposes:
i think the issue was caused by spam bots who found and used the email field at /comment-subscriptions/
without any attributes i got a zillion emails. same with the attribute &expired=1 set (they both trigger different includes). guess the others also caused issues, but am not too deep in this plugin (as you are..) so i dunno how to test it. i’m good for now.. thanks

btw. i now changed all the includes in that file, since i also had issues inside the if ($error_exits) { condition.. also works fine now.

eg.
$include_post_content = include_once WP_PLUGIN_DIR . '/subscribe-to-comments-reloaded/templates/key_expired.php';

• This reply was modified 4 years, 4 months ago by jnz31.
• This reply was modified 4 years, 4 months ago by jnz31.