Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

RichM

Administrator Donate to Canal World
  • Content Count

    860
  • Joined

  • Last visited

Community Reputation

0 Neutral

4 Followers

About RichM

Profile Information

  • Gender
    Male
  • Location
    UK

Previous Fields

  • Occupation
    IT
  • Boat Location
    Bromsgrove

Recent Profile Visitors

5724 profile views
  1. No idea. Will look into it. They are not duplicates, each entry is posted by a different member. - Appreciate that it may seem unnecessary for a topic to be listed more than once irrespective of how many people have posted in the topic recently but on the other hand it gives indication of any topics which have been very active within the last hour. That said we will see if we can remove this behaviour as we've received a fair amount of negative feedback about it.
  2. I thought as much though we have a select few who complain if we do anything without announcing it, so here we are...
  3. Hello, We have updated the forum software to Invision 4.4.3 and subsequently 4.4.4 to apply a bug fix release. This is not a feature release and as such the overall look, feel and functionality of the site remains unchanged. Should you encounter any oddities or have any questions, do let me know. For anyone who is interested, the release notes as provided by Invision are as follows: Technical Details Security Fixed an XSS concern deleting members in the AdminCP. Fixed an XSS concern managing Downloads versions from the changelog view. Fixed a minor XXE possibility in blog RSS imports. Core Added support for [Emoji 11](https://emojipedia.org/emoji-11.0/) emojis Added logging for errors communicating with Spam Defense. Added a pre-installed Giphy key that can be used for all Invision Community installations. Improved usability and display of date-based member filters. Improved account validation process to prevent accounts being inadvertently validated by scrapers and bots, and to improve the user experience when following a validation link that is no longer valid. Improved the opcache comments check on the REST API Reference page. Improved sending bulk emails via SendGrid. Improved post before register permissions when allowing guests to create content, but not members. Clarified the registration completed email when no local password has been set. Fixed an issue where members may not be marked as complete, and thus will not show within the community, in some circumstances. Fixed the Posts Per Day group setting not applying consistently to all content. Fixed an issue where click tracking may not be applied to all links in emails sent. Fixed the email statistics charts in the AdminCP showing incorrect data when viewing weekly charts. Fixed an issue where the inbox list may be stuck showing a spinner when canceling a search in the personal messenger. Fixed an issue where folder counts may show NaN after deleting a folder in the personal messenger. Fixed an issue that may occur when deleting/moving login handler related images. Fixed 'post before register' content submissions not incrementing the user's post count if pre-moderation is not required. Fixed an issue related to 'post before register' where 'next unread' item links may show when there isn't any new content. Fixed the digest task looping on a follow attached to a deleted member. Fixed the `PruneMembers` background task from endlessly looping in certain circumstances. Fixed disabling password changes in the AdminCP settings not removing the link to change your password on the Account Settings overview page. Fixed issue where lazy-loaded images in warn reasons would prevent warn reason from automatically updating when new reason was selected due to incorrect editor 'dirty' status. Fixed a niche issue where promoting an item may show an auto scheduled time from the past. Fixed an issue where the button to change a members profile photo would still show on their profile when they do not have permission to upload profile photos. Fixed an issue where public clubs would show the member count in several locations. Fixed an edge-case issue with redirecting old non-rewrite FURLs after enabling rewrites. Fixed issue checking signature image dimensions when using 'insert existing attachment' when using Amazon S3. Fixed an issue where the frontend upgrade notice wouldn't disappear once dismissed. Fixed an issue where cover photos might disappear shortly after displaying. Fixed an issue with lazy load placeholders when added to existing content. Fixed a layout issue with the mobile pagination buttons. Fixed an unnecessary redirect when viewing a club. Fixed a potential timeout running the cleanup task. Fixed Elasticsearch being able to be set up with version 7 (which is not yet supported). Trying to do that will now show an error message. Fixed an issue where moved links may show in the topic widget. Fixed an issue where a member registering with an auto-detected language would revert back to the default language after registration. Fixed an issue where the latest activity tooltip would state "online now" when the member was offline. Fixed broken login form. Fixed status pagination loading a full page instead of comments only. Fixed non-latin characters in the URL showing incorrectly when moving between pages. Fixed an issue where the approval queue may show content in the wrong order. Fixed an issue where the guest signup block title and text was reversed in vertical view. Fixed an issue where custom friendly URLs would not use the newer `/page/2/` pagination format. Fixed an issue where club pagination in user profiles was showing the wrong number of pages. Fixed an issue where a Redis failure caused an uncaught exception. Fixed an issue where the Clubs REST API would throw an error if commerce isn't installed. Fixed an issue where online user lists may be empty following a Redis crash. Fixed an issue where incomplete member registrations were not cleared correctly. Fixed an issue where Post Before Register Followups were sent out immediately rather than delayed. Fixed an exception that prevents storage handler changes from being saved properly. Fixed an issue where the 'Failed Emails' AdminCP notification may not be removed properly. Fixed an issue where the "Anonymous login" checkbox was incorrectly checked. Fixed an issue where PBR content would be left in the database for uninstalled applications. Fixed a rare issue where a template disk cache could corrupt and affect templates loading. Fixed an issue where members created via the ACP weren't marked as completed. Fixed an issue with Flickr video embeds showing as photos. Fixed an issue with notifications not showing as unread. Fixed an issue where the exact profile field search option had no affect. Fixed an issue where the default country was not correctly set in address form inputs. Fixed an issue where the guest teaser would not show on the comment form in some circumstances. Disabled Grammarly from checking editor fields to prevent Grammarly from breaking HTML and causing broken posts. Disabled preloading of notification sound to speed up initial page load. Disabled concurrent comment merging in status replies. Removed post content from Post Before Register reminder emails to prevent spam. Upgraded CKEditor to 4.11.4. Updated LinkedIn login handler to use the LinkedIn v2 API. Improved performance when merging two comments with duplicated member reactions for large sites. Improved performance when working with edit history logs. Improved security of how passwords are handled in the code to decrease the likelihood of a password being included in an error log. Improved the display of the upgrader confirmation page. Improved performance of the latest activity stream shown on user profiles. Improved anonymous log in tracking to resolve an issue with "Since my last visit" activity streams Improved the UX configuring moderator permissions for clubs, including the ability to disable club-level moderators. Improved database error reporting in certain error situations. Improved performance of a 4.1.8 upgrader step. Changed AdminCP notifications for "A new member has completed registration" and "A member is flagged as a spammer" to show all applicable members grouped into a single notification, rather than a separate notification for each member. This change gives a significant performance improvement for sites which have lots of new registrations. Fixed multiple formatting concerns with custom profile fields. Fixed an issue where restoring soft-deleted content would throw an exception under specific circumstances ( e.g. when there was no record in the soft deletion log ). Fixed an issue where the member group restriction to require one piece of approved content before users can bypass content moderation was not correctly applied to posts made before registering. Fixed an issue where deleting a member's content and then deleting the member may result in the content not being removed. Fixed SVG images breaking when served through the built in image proxy. Fixed an issue with profile completion if you choose not to upload a profile photo. Fixed third party processor information not showing when users are forced to reaccept an updated privacy policy. Fixed the "Remove followers from uncommented content" setting not working. Fixed an issue where clicking to delete a member twice might result in all status updates being removed from the search index. Fixed an issue where copying content from one area with an attached image and pasting into another area may result in a broken image. Fixed an issue where allowing a user to moderate comments, but not items, would result in an error when using the multi-moderation menu. Fixed inability to edit profile fields by members if the field was not displayed on the profile. Fixed invalid HTML in the quick search form. Fixed an issue where a comment or post made before registering which requires moderator approval after the registration is completed may not update the container flag to indicate that comments within the container require approval. Fixed an error where the member view in the AdminCP may become broken if the member history for the user includes an old subscription group change and Commerce is not installed. Fixed an issue where broken letter photos may be displayed in emails. Fixed an issue with clean up tasks where they may try to delete a member that doesn't exist. Fixed an error that can occur if you double click the "unfollow" button quickly. Fixed autosaved content in the editor not clearing out when it was deleted within the editor. Fixed an issue where MFA while the login would send 3 'new device' emails to the member instead of only one. Fixed an issue where attachment links inserted into content may have a hard coded URL. Fixed an upgrade issue where custom file storage configurations in 3.x may not be preserved correctly when upgrading to 4.x. Fixed an uncaught exception when visiting a specifically malformed follow link. Fixed attachment bbcode tags not converting correctly when upgrading from version 2.0 or older. Fixed the About Me default custom field not showing on new installs. Fixed email statistic charts so they report more accurately. Fixed issues with performing advanced member searches in the AdminCP when multi-select custom profile fields are present. Fixed a minor inconsistency with group name formatting. Fixed an issue rebuilding certain meta data in Elasticsearch. Fixed an issue where items and comments queued for deletion or submitted by a guest prior to registration are returned via the REST API. Fixed an error when searching a specific search string. Fixed a possible error that can occur during login when using the post before register feature. Fixed the Notification Settings form in the Admin CP so that it can save properly. Fixed an issue where Login Handlers were shown out of order. Fixed an issue where the canonical link HTML tag may include unnecessary query string parameters (i.e. filters). Fixed an issue where AdminCP settings search results were not always highlighted when clicked on. Fixed an issue where the pagination for comment and review areas wouldn't link directly to the comments area when Javascript is disabled. Fixed an issue where content item and comment widgets would show content from not specified categories. Fixed an issue where editor auto saved content may not be removed. Fixed an issue where some content may not show a report link. Removed the hide signatures toggles from guests when they are able to see signatures. Prevented search engine spiders from following the cookie notice dismissal link. Removed poll votes from showing in the All Activity stream. Removed ability to copy theme settings. Removed the unread indicator in several widgets because it can't be used there because of the widget cache. Removed the ability to toggle cover photos in clubs list when no image was uploaded. Fixed an issue where the support tool could incorrectly report undiagnosed problems. Fixed missing images when lazy loading is enabled in several areas. Fixed an HTML validation issue with mini-pagination next to multi-page content item titles. Fixed an uncaught exception which is thrown by the Admin Notification System. Fixed member validation display issue in ACP notifications page while mobile. Fixed attachments being added to an editor which has attachments disabled. Fixed an issue where a display name sync error may be displayed on the AdminCP member profile. Fixed two language strings where countries have changed their names: Macedonia is now North Macedonia and Swaziland is now Eswatini. Fixed some broken messenger related links. Forums Fixed a niche issue where the 'Delete Legacy Posts/Topics' background task may not work when ran via CRON. Fixed an error when moving topics in fluid view. Fixed a database error that could occur when archiving old posts. Fixed a duplicated error code in the topics REST API endpoints. Fixed images used in forum rules not displaying when image lazy loading is enabled. Fixed a potential upgrade error when reformatting forum rules during the 4.0.0 upgrade routine. Fixed a duplicated error code in the topics REST API endpoints. Fixed images used in forum rules not displaying when image lazy loading is enabled. Fixed a potential upgrade error when reformatting forum rules during the 4.0.0 upgrade routine. Gallery Fixed an issue where past reputation for image comments and reviews no longer displayed. Fixed browser scrollbar disappearing while editing Gallery image details in some cases. Fixed image carousel widgets not displaying correctly in certain circumstances. Fixed an issue where uploading on small screens caused the status to overflow outside of its box. Fixed an issue where images may show as unread incorrectly in streams. Changed the reputation type flag for album comments and reviews to resolve bugs where the reputation may be mistakingly treated as if it belongs to an image comment or review. Fixed an issue submitting images to an album if the category requires moderator approval. Fixed an error that can occur when downloading the original image in Gallery if the original image is missing on disk by forcing the largest available size to download instead. Fixed image lazy loading not working correctly in category rules, descriptions and custom error messages. Fixed the submission dialog box potentially showing an incorrect dialog title. Fixed an issue where uploaded videos could not be played in the lightbox. Fixed editor showing twice for each image during submission. Calendar Fixed an issue where recurring events may show on the wrong day in Calendar. Fixed an issue where all day events specified an incorrect start and end time in search engine markup
  4. We don't have new features with every update, most updates include bug fixes. However, the feature in question (i.e. guests being able to post) is referenced via a link in the topic below: The link containing a full list of features will take you to this page which in turn mentions "4.4: Increase visitor registrations with Post Before Registering". This is the change in question. Rich
  5. This confuses me as the hosting company we use do not contact our members. Is it possible to take screenshot of the email and PM it to me? If you have any reason to suspect your computer or accounts have been compromised it’s a wise idea to scan your machine as mentioned. I also recommend Malwarebytes but also do a full AV scan in addition to a malware scan. If you share a computer I also recommend having your own windows or apple user account for use when logging in to your computer(s) Having multiple people sharing one account is not really wise, though not uncommon...
  6. That is also plausible though a few other members have reported the same thing recently too
  7. Ignore it. It’s likely either a spam bot or a troll purposely trying to login with incorrect credentials and thus prompting the notifications you receive. It is worth noting that you will also be notified by email in the event that someone does login from a new device. This is the only time you need to be concerned. Should you receive such an email and presuming you did not login from the device, I’d recommend checking your computer for malicious software and also check your email account has not been compromised. I could disable the alerts (for everyone) if need be but that won’t stop anyone or anything from *trying* to login as you using incorrect login details, it just means you wouldn’t get to know about it.. The other option is to create an email rule that moves the email with the subject in question to your deleted items folder.
  8. Statistically and without meaning to tempt fate, our up time overall is actually quite good. (stats below) Some of the downtime encountered recently was the result of server maintenance that did not go as planned/expected and was no fault of the forum software. In fact, it was my fault! While the server is hosted on a fast VM with 4 CPU cores, plenty of memory and SSD storage, we do not run in a cluster environment which means that some maintenance tasks will inevitably require the site to be taken offline. On the rare occasion (e.g. recently) some tasks can have unintended implications/side-effects. However this is the nature of IT, unfortunately... We therefore try to do this outside normal hours to minimise impact though given we are non-profit and given I do this for free, it's also limited by my availability. (sorry!) Having said that, our stats don't appear too bad at all: (Monitoring checks are performed automatically by a third party who check for HTTP status codes every 5m) As for the spam attacks, again I would not blame the forum software. Spammers are constantly finding new ways to circumvent anti-spam measures otherwise they will lose their game.. As such, fighting spam is an endless battle. We have also implemented other measures beyond that of what any forum software can provide to help combat this. However, that's not to say we won't encounter another spam attack, nor is it to say our current measures put in place will protect us forever. - they won't. Spammers will advance their tactics which means we will inevitably have to do the same. I don't believe any site with user-generated content is immune to this even if it may go unnoticed by many. Equally, all sites encounter problems, even if you may not notice them. Even the web giants such as Facebook and Instagram (which utilise similar software & infrastructure technology albeit on a much much larger scale) have encountered outages recently, some lasting days! If anyone wants to post a poll & discussion topic to see how much interest there is in switching to vBulletin, we invite them to do so. - If there is enough member support then sure I will bring it to Daniel's attention and recommend we consider. Without that, it's a non-starter considering cost along with the work involved especially given what we have currently does work. Rich
  9. Totally agree with you. I have done the migration previously on other forums and do similar work during my day job. That said, there will always be teething issues with any migration like that. vBulletin is better all-round, sure. Although Invision does have its pros. Problem is that we made the decision to go from IPB 3.x to 4.x about 2 years ago which was a radical change and not really one we could delay much longer at the time. If we were to migrate to vBulletin, it will introduce radical change again in terms of functionality, software behaviour and UX design. Now I personally have no issue with that but seeing as how some users express dismay over the smallest of changes, I question how well it will be received, at least initially. - To be frank about it. I think maybe when Invision 4.x reaches end of life (not anytime soon) we may be in a better position to think about switching but even then I think there will be a lot of resistance from some members, so it's certainly not really a decision I want to call.
  10. It has been like this for well over a year. The PM system is threaded like most modern messaging systems (not email), whereby the conversation is all in one thread. Sorry but we do and will continue to use current software. All our software is kept up to date and we certainly won't be falling behind on this while I'm responsible for looking after it. With our current approach, yes you will see more in the way of change as we regularly apply minor software updates as and when released by Invision. That said, the majority of the changes will be subtle. The alternative is to do what was done in previous years - i.e. maintain a legacy version but if we were do do that, sooner or later the time will come to update and in doing so, it will introduce radical change as a consequence. In my opinion this is worse in terms of user experience which is why we introduce small but frequent changes, rather than big changes over a longer time period. That aside, we won't be running or maintaining legacy software for a number of other reasons.
  11. What typically happens after the boat is re-floated? I guess it has to be completely gutted out inside, treated/painted and refitted?
  12. Hi all, Just wondering if anyone has had any further issues receiving emails from us? We migrated to a new email server (details here) to address this, so I'm hoping it has done the trick. - The mail server logs look much more promising but the proof is in the pudding as they say. All feedback appreciated. Thanks RichM
  13. It was unrelated to that change. Normally when we carry out site maintenance we will have a small list of tasks to do. Unfortunately the issue with the site search was not expected and happened as a result of a server software update. I had to completely remove the search engine from the server, reinstall it and re-build the search index. I then had to do it all over again because the version of the ElasticSearch engine we applied was incompatible with the forum software, unbeknown to me... It would have helped if Invision published this info though I will take blame for it.
  14. Hi all, We've received reports from our members to advise that emails from us are not being received, or are going to spam/junk folders. As one of the steps we have taken to address this, we have moved to a third party mail provider to help improve the deliverability of the emails we send. Further to this change, we recommend reviewing your email notification settings which you can do by clicking the link in my signature below. Of course this does come at an additional cost to us as a non-profit discussion forum & community. With that in mind we appreciate all donations received from our members. Please feel free to make a donation which you may do so by clicking here here. Thank you RichM
  15. No problem. Took longer than I hoped to fix but looks to be OK now
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.