nosnurg

Ah that’s what you meant by Custom Date Range. No all my feeds are set to ‘Grid (Month View)‘ in the settings.

To be honest I haven’t really grasped what the display mode in the feed settings actually does because I always set it in the widget or the shortcode. Clearly it has more significance than I realise.

G.

The calendars are displayed using the widget or shortcodes like [gcal id="1581,1582"] or [gcal id="1581,1582" display=list]. The calendars themselves seem to display fine in both grid and list mode whether for a single feed or multiple feeds, it is just that if there are multiple feeds they also throw the notices …

Notice: Undefined index: 1581-1582-1583-1584-1585-1586-1587 in [...]/wp-content/plugins/google-calendar-events/includes/misc-functions.php on line 50

Notice: Trying to get property of non-object in [...]/wp-content/plugins/google-calendar-events/includes/misc-functions.php on line 50

… and I like to display them on the web page in my environment so I can see what is going on.

It is tripping up on the code …

if( $range_start === null ) {
		$range_start = $d->feeds[$feed_ids]->feed_start;
	}

… because $feed_ids is e.g. 1581-1582-1583-1584-1585-1586-1587 when multiple lists are being displayed and the $d->feeds[] array indices are individual feed IDs like 1581 or 1582. So whatever $range_start is used for, it isn’t getting set correctly when there are multiple lists being displayed.

G.

No I’m afraid not. The code causing the problem is the line setting ‘range-start’ if it is null. It is using the hyphenated string of feed IDs as an array index and I suspect it just wants a single feed ID. I’d paste it here but text selection on my tablet is playing me up.

The grid still seems to display the events fine, though I only gave events in one of the feeds at the moment so I’m not 100% sure, it is just whatever that line does throws up a warning notice.

G

Could I just follow up on Sba Nyft’s post and the comment “After enabling every output about errors (WP debug mode) I received no errors/notice/warning”? I was wondering why I wasn’t seeing any WP Debug messages on my theme at all and then today I discovered that it was Social Media Auto Publish that was preventing debugging working. So that might be why you didn’t see any errors.

@netcentsii is that with the .htacess file you show above, or with the RewriteRule .* - [E=noabort:1] rule added to it?

Adding

<IfModule litespeed>
RewriteEngine on
RewriteRule .* - [E=noabort:1]
</IfModule>

to the .htaccess in my WordPress root does indeed seem to do the trick for me, thankyou. I see it all over t’internet now I know what I am looking for. I don’t think it is the sort of thing I want permanently in the WordPress root .htaccess, but it does the job for me. I don’t know if there is anyway of making it more specific to Wordfence because I haven’t got my head around what is going on at the moment.

Mark, could there be an option for Wordfence to add this on the fly when it needs to do a scan and remove it afterwards, or do you think it is perhaps a little too specific a fix?

G.

I don’t have anything saying ‘entered fork’. The closest I have is ‘Scan process ended after forking’ (see https://pastebin.com/9jG9jEqy ).

Graham

Mark,

I’ve been using the debug options. After the initial setup all it shows is a list of files being scanned and that list just stops updating. The scan starts at e.g. May 21 11:49:12 and stops updating at May 21 11:49:41. That’s 29 seconds which is the process execution limit I have set. Had I left it to default it would stop after 15 seconds.

The scan summary shows the ‘in progress’ indicators as if something is happening but I don’t know what controls the display of those.

I only have access to the CPanel error log and that shows absolutely nothing of interest. I don’t know if there are other logs I wouldn’t get to see.

G.

Duplicate post …

I suspect we aren’t but my installation is on EZPZhosting, who are CPanel based using LiteSpeed, and I’m in the Kent data centre.

G.

Sorry, I didn’t intend to hijack the thread by the way, I just inadvertently breached etiquette and then it seemed less damaging to widen the breach with some hopefully useful information.

G.

More info:

I am running with the medium security setting.

My shared hosting is configured for a maximum execution time of 30 seconds and 128 Mb of memory. Running the memory test says 90 Mb was requested and it was able to get 82.5 Mb which it seemed quite happy about.

If I leave the execution time blank at the default the logs report:

getMaxExecutionTime() returning half ini value: 15
Got max_execution_time value from ini: 30

The scan then runs for 15 seconds and stops showing anything else happening.

If I set the execution time to 29 seconds then I get:

getMaxExecutionTime() returning config value: 29
Got value from wf config maxExecutionTime: 29

The scan then runs for 29 seconds and stops showing anything else.

It doesn’t seem to make a significant amount of difference whether I reduce the memory option to 75 Mb or double it to 512 Mb (I wouldn’t expect the latter to make a difference as presumably the internal limits are detected). 75 Mb actually words a tad better than 82.5 Mb but neither work as well as leaving the default alone.

Turning off ‘Scan for signatures of known malicious files’ allows the scan to process more files but it just means it is doing more in the time it has available.

To me it seems like something is going wrong when a new process is being forked but whatever that something is doesn’t show in the activity log. For all I know, it being a shared server, the scan could be chugging along quite happily but not updating the activity log so I don’t know about it.

I have had no joy with getting a scan to complete on a LiteSpeed server either. The first few times it was doing about four things at once (core, themes, plugins, malware) but not saying anything about progress with files in the details. By telling it not to do themes or plugins and various reducing the execution time to 15 seconds and playing with both increasing and decreasing memory size I got it to tell me it was scanning files and eventually it built up to 1400 files but that is it. There are no errors to be seen anywhere that I have access to, it just seems to stop making any progress.

Wow, I didn’t realise that bug still persisted, it has been apparently been known about for five years or so and I thought it was supposed to have been patched.

Anyway I don’t know if it will help in the OP’s case, but wp_list_pages currently has other somewhat odd behaviour that can be exploited.

If you tell it to exclude a parent page with e.g. exclude=74(I’m talking about a top level page here, I haven’t experimented further down the hierarchy) then its children still need to be displayed so they get listed with the top level pages. However if you add e.g.depth=3 the exclude starts behaving like exclude_tree is meant to and all the children get hidden too. To me that is a bug and I’ve reported it as such, but it is quite a handy one at the moment.