edanwp

My previous fix in em-calendar.php was wrong, it should be:

$next_url = esc_url_raw(add_query_arg( array_merge($link_args, array('mo'=>$month_next, 'yr'=>$year_next)),'/' ));
.
.
$calendar_array['links']['today_url'] = esc_url_raw(add_query_arg( array_merge($link_args, array('mo'=>$today->format('m'), 'yr'=>$today->format('Y'))),'/' ));
.
.
$calendar_array['links']['previous_url'] = esc_url_raw(add_query_arg( array_merge($link_args, array('mo'=>$month_last, 'yr'=>$year_last)), '/' ));

How can I get the developer’s attention to apply the fixes? It’s frustrating to see the number of wasted requests crawlers are doing because of it.

[20/Jun/2024:17:11:27 +0000] "GET /57105/?id=276971852&ajaxCalendar=1&mo=11&yr=2024 HTTP/2.0" 200 27482 "-" "facebookexternalhit/1.1 (+https://www.facebook.com/externalhit_uatext.php)"
?
[20/Jun/2024:17:11:27 +0000] "GET /category/test/page/5/?id=827964334&ajaxCalendar=1&mo=6&yr=2024 HTTP/2.0" 200 29844 "-" "facebookexternalhit/1.1 (+https://www.facebook.com/externalhit_uatext.php)"

Maybe can completely remove the “href” since it’s all done JS anyway.

Thank you for your answer.

My website have tens of thousands of pages. On a regular day i have only few hundreds users viewing few hundreds pages, but if a crawler decides to crawl the full website, there is a lot of pages for it to view.
A few days ago I had such crawler which resulted in retrieving “layout.html” over 190,000 in January. My homepage was accessed less than 7000 times this month.

Logs from the last 3 days (removed the server ip)
[~/logs]# find . -mtime -3 | xargs zcat 2>/dev/null | grep [ip-removed] | awk -F ‘”‘ {‘print $2’} | sort | uniq -c | sort -rn | head -10
124864 GET /wp-content/plugins/simple-lightbox/themes/baseline/layout.html HTTP/1.0

My hosting (SiteGround) say that this call is counted as “execution” which is a limited resource in my account.

Oops. After reading other threads, I re-saved the password and now it works.

Too bad there wasn’t any decent error showing up about the password being decoded wrong.

I have the same error, v1.1.7

Worked great until few days ago, now I get connect failed.

Hosted on DreamHost

While I’m here, may I suggest that in cases of failures the emails will be saved in a text file?

I probably lost a few contact-us due to this error (and it can always happen again, from hosting issue, password change and etc’)

There is a link to the fix in my message + full explanation about the cause of the issue.

Fix available here: https://pastebin.com/3Um1HKtF (based on 1.2.4)

Hi,

I posted my reply previously on an already resolved ticket, so maybe it was missed.. sorry for re-posing it, but I think it will resolve this issue.

Regarding 1.2.4 – The new fix/version is ignoring users who call “get_imgmap_frontend_image” directly from the theme.

For backward compatibility, it’s better to create a new function to put into add_shortcode, and make “get_imgmap_frontend_image” call that function.

Also, new code ignores the element id that was passed as parameter, that can break CSS rules that were based on that name.

Fix for the above 2 issues is here: https://pastebin.com/3Um1HKtF

I had the same issue like stevertr.

The new fix/version is ignoring users who call “get_imgmap_frontend_image” directly from the theme.

For backward compatibility, it’s better to create a new function to put into add_shortcode, and make “get_imgmap_frontend_image” call that function.

Also, new code ignores the element id that was passed as parameter, that can break CSS rules that were based on that name.

Fix for the above 2 issues is here: https://pastebin.com/3Um1HKtF