WPIntell

Source evidence

php warning

lazysizes · support · 2019-05-28T08:43:00+00:00

lazysizes plugin evidence original source source API
questionsentiment
mediumseverity
0.78relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 29 rows with source links

20.7% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

23 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
julian_wave resolved
Hi I’m seeing a php warning Warning: preg_match(): Unknown modifier '>' in /home/survivorsnetwork/public_html/wp-content/plugins/lazysizes/class-lazysizespregreplace.php on line 168 This is on the default calendar page created by The Events Calendar plugin. So far I have not seen the on any other pages. Is there anything I can do about it? The page I need help with: [ log in to see the link] Hello, Thanks for reporting. I’ll look into it and see what I can do. It might be a bug with my plugin that’s only visible in certain circumstances, like when using that calendar plugin. Other than the warning, it shouldn’t cause any problems at least. Again, I’ll see what I can do about it. – Patrick Sletvold I’m able to reproduce by simply activating the plugin, so a fix is hopefully not too far away. Should be fixed now, can you try version 1.1.0 and see if that is indeed the case @julian_wave ? – Patrick Sletvold This reply was modified 7 years ago by Patrick Sletvold . It seems to be fixed with this new update, thanks.

Comments

4 shown
Patrick Sletvold 2019-05-28T13:11:00+00:00

Hello, Thanks for reporting. I’ll look into it and see what I can do. It might be a bug with my plugin that’s only visible in certain circumstances, like when using that calendar plugin. Other than the warning, it shouldn’t cause any problems at least. Again, I’ll see what I can do about it. – Patrick Sletvold

Patrick Sletvold 2019-05-30T12:44:00+00:00

I’m able to reproduce by simply activating the plugin, so a fix is hopefully not too far away.

Patrick Sletvold 2019-05-30T15:36:00+00:00

Should be fixed now, can you try version 1.1.0 and see if that is indeed the case @julian_wave ? – Patrick Sletvold This reply was modified 7 years ago by Patrick Sletvold .

julian_wave 2019-05-30T15:44:00+00:00

It seems to be fixed with this new update, thanks.