nmv
Forum Replies Created
-
I had the same issue. Logging out and back in solved it with no changes to anything else.
Forum: Plugins
In reply to: [Redirection] 404s Not LoggedI was using a feature in my theme that redirects 404s to another page. I disabled that feature and installed the “404page – your smart custom 404 error page” plugin instead and that resolved the issue.
Thank you for your help!
Forum: Plugins
In reply to: [Redirection] 404s Not LoggedThanks for the quick reply! I believe logging is enabled based on the following settings on the Options tab:
Redirect Logs: A Week
404 Logs: A Month
IP Logging: Full IP Logging
Redirect Cache: An Hour
REST API: Default REST API (Note: I have tried all options here. I have also tried disabling caching and the security plugin)An invalid URL would be: https://rocstarts.com/badurl
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Calendar displayed twice with WP 4.7This issue is marked as resolved but the resolution is either to not use shortcodes or downgrade WordPress. Neither of these is a good solution when there are other elements on the page. Is there a solution to keep the shortcode with other elements on the page while showing only one calendar? Even something as simple as adding a separate CSS class to the 2nd calendar would be helpful since it could at least be hidden.
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Calendar displayed twice with WP 4.7Yes. It is required because there are other elements before and after the calendar.
- This reply was modified 7 years, 10 months ago by nmv.
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Two Calendars showing on pageIs there a solution for this when a shortcode needs to be used on the Calendar Page? Upgrading to WP 4.7 causes two calendars to be displayed (see https://pca.nmvhosting.com/calendar/). Sticking with WP 4.6.1 displays only one calendar (https://niagarapca.org/calendar). Changing themes, deactivating plugins, and switching browsers did not fix the issue.
I was able to resolve this error by unchecking “Filter Suspicious Query Strings in the URL” in iThemes Security (under “System Tweaks”).