pandammonium

Speaking of errors, I got the filename wrong; not sure how. Amyway, this is the correct filename:

/user/wordpress/wp-content/themes/my-theme-of-choice/wp-content/plugins/events-manager/em-functions.php

Sorry about that.

The bug hasn’t been fixed in v.6.4.6.4.

This bug is not fixed in v6.4.6.3.

Function em_output_events_view() is now on line 896.

Function em_output_locations_view() is now on line 958.

This bug is not fixed in v6.4.6.1.

The line numbers of the affected functions are the same as in v6.4.6.

This bug is not fixed in v6.4.6.

Function em_output_events_view() is now on line 895.

Function em_output_locations_view() is now on line 957.

Thanks to my host tweaking things in some magical way, EM seems to work now (apart from this bug).

I’ve upgraded PHP on my server to v8.0, and it seems to work ok (apart from a location mysteriously not showing up in the shortcode; this was fixed by going to the event editor and resetting the location).

I’m afraid not. The error message displayed on the admin web pages was vague, and I don’t have error logging switched on.

I think after adding the watermarks, I used the Regenerate Thumbnails Advanced plugin, then I tried to restore the images using Easy Watermarks. After that, some – but not all – of the images that produced errors were missing from my uploads/ folder. Luckily, they were in the ew-backup/ folder, so I used the Enable Media Replace plugin to put them back (and to replace the images that Easy Watermark wouldn’t).

I’m sorry I can’t be more helpful, but I do appreciate your desire to find out what happened. Thank you

@ajay Got it. Thanks for clarifying.

Yarrp allows the user to exclude categories and tags. Is this the sort of thing being requested here? Might be worth having a look to see how they do it.

Hello Lufrutta,

I’m delighted you’ve downloaded Blipper Widget and have found it useful – thank you very much. I very much appreciate your lovely review, and I’m honoured by the star rating. I’m happy that you like the design features, too.

Regarding your comment about opening the blip journal in the same browser tab: it is a design decision that I am not likely to change. I made this decision for two reasons: choice and security.

*Choice*

Often, when I’m reading something online, I follow link after link that opens in a new tab. This can cause many tabs to be open at once – sometimes so many that I can’t find the original tab (especially if there were already several tabs open) or I can’t read the tab title any more because the tabs are too narrow (and I don’t recognise the favicon). This behaviour also breaks the back button: you can’t just press ‘Back’ (or ‘<‘) to return to the previous page.

I prefer to let the user choose whether to open a link in the same tab or a new tab. If the user prefers to be able to navigate easily to the original page, they need simply to click on the link, then click the back button when they’re done. However, if the user prefers to open the link in a new tab, they need only to right-click the link and select the ‘Open Link in New Tab’ (or similarly worded) option. It’s an extra click, but I think it’s worth it for the security it brings.

*Security*

Browsers are told to open links in new tabs using the target=”_blank” attribute in the link’s anchor in the HTML that creates a given web page. This code allows nefarious websites to hijack the original tab and to phish for sensitive data in that tab. Blipfoto is not a nefarious website, but there’s a chance it could be hacked by nefarious people. Hackers could change the Blipfoto website so that acts in a nefarious way.

There are ways to overcome this security flaw, but they are not necessarily supported by all browsers. Therefore, I prefer not to introduce the vulnerability in the first place.

I hope you can understand and appreciate the reasons behind this decision, and that you get lots of pleasure from using Blipper Widget in the future.

Thank you again for downloading and using Blipper Widget. I’ll look forward to seeing you on Blipfoto soon!

Cheers,
pandammonium

Sometimes I wonder if caching is more trouble than it’s worth! I wish I’d thought to clear the browser cache beforehand — but one cant think of everything all the time.

Thanks for looking into it, anyway. I’m just glad it all works again and I can continue to admire my newfound secure padlock symbol in the browser address bar ??

Thanks for taking the time to find the fix and to share it, Rodilard. Works a treat, now.

I hope the developer fixes this in the next update.

It’s not the <ul> tags that’s the problem; it’s the incorrect use of the <script> tag by WordPress. WP writes out the following:

<script lang='javascript'>&hellip'</script>

which is invalid, instead of using the value:

type="text/javascript"

like you’re supposed to (according to W3C).

This is particularly irritating, and I, for one, would like to see it fixed.

thebluntprophet: what you said works a treat – thanks ??

I get the same problem with importing from Blogger. I think all the errors are variations on a theme, as I’ve had them all.

Using BlogSpot instead of ftp definitely works. I suggest that somebody renames this importer as BlogSpot and writes a separate importer to do Blogger-by-ftp.

What I don’t get is how come importing a Blogger-by-ftp blog imports fine if you’ve got a wordpress.com blog, but doesn’t if you’ve downloaded the WordPress software.

charlottesweb: sorry, no clue. Hope someone else does, though. I would try republishing to the Blogspot site, logging out of Blogger, then trying to import it again. I expect you tried that, though!