Jump to content

Grant_B

Clients
  • Posts

    68
  • Joined

  • Last visited

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by Grant_B

  1. We are having the same issue with posts that need to be approved that are stopped by the spam analysis tool. We reported it last Wednesday but haven't had a resolution yet so for now we've had to turn this feature off as we were having lots of topics stuck in limbo, unable to be approved.
  2. Spam levels are extraordinary high at the moment - I know invision are working on improvements but one thing I think would be useful is downrating in the spam system temporary email addresses - there is a maintained list here: https://github.com/disposable-email-domains/disposable-email-domains Many of the spammers I have seen recently are using email addresses in this list and it is rare for legitimate members to use disposable email addresses so it would be great if the spam defence could automatically notch an account up a point if it uses a disposable email address which for us, would then put the member on moderated posts which would catch a lot of these. It would also be good to see some sort of spam scoring to posts as well to be able to set a trigger for new members if there posts reach a certain spam level score moderate them first - again a lot of the spam we are seeing is very obviously spam so it shouldn’t take much intelligence to sift these out - for example I’ve caught a lot today just by putting ‘coinbase’ in our word filter and making those go straight to moderated posts.
  3. The new patch has fixed the login issue but I am also seeing the problem with the guest terms popup coming back everytime for guests even if they accept it.
  4. It introduced some other issues so I had to put it back but I found turning off the guest popup terms fixes the issue albeit as a temporary measure.
  5. No - nothing like that. I don’t understand the code well enough so this might be talking nonsense but… in the new function added to request it checks the logged in users language in order to check the guest terms bar value - if this is called before the user session is initiated because it hasn’t yet got to that cookie will it stop it getting initiated later on in the process flow?
  6. I do now and the issue goes away. With it enabled the fault occurs - it doesn’t think the user is logged in when starting a new session (browser closed / opened or session expired) - on the second visit of the new session it does log the user in so the cookies are working it’s just the first visit shows then logged out.
  7. I'm sorry for all the posts - I didn't like running modified code and noticed one of the parts that seemed to be causing issues referenced the 'guest_terms_bar' setting so I put all the code back to standard and switched off 'Show terms of service confirmation or cookie bar to Guests?' and the issue has gone away. I don't know whether this means this is an invision bug that they need to look into, a setting issue with our forum or a template issue. I did switch to the standard theme but the issue continued.
  8. Using the older Request.php caused some other errors so I reverted to the new one but this still seems to be where the issue lays, at least on our site.
  9. Digging deeper - I noticed that system/Request/Request.php is one of the files updated in the patch released after 4.7..11 - reverting back to the version in 4.7.11 the issue is resolved. It looks like a cookie issue with recreating the session - it doesn't seem to take on the first visit when the session cookie has expired or the browser closed but does work on the second click. Reverting system/Request/Request.php seems to have resolved this so hopefully this helps you guys work out the issue and release an updated patch.
  10. I did the 4.7.11 this morning and then did the patch update about 4-5 hours ago - I didn't receive any reports of this issue until after the patch so I wander if the patch has caused this?
  11. Since updating to 4.7.11 earlier today members are reporting that they have to keep logging in despite ticking the remember me option. I have replicated this myself on my iPhone - if I close safari completely and then open it the forum shows me visiting as a guest but as soon as I click on login or any other link then it logs me back in automatically. It’s almost as if initially it ignores the saved cookies but once you click on something it works correctly? Anybody else seeing anything like this?
  12. It looks like it's a Windows / DNS issue - thread about it here:
  13. An external service being down shouldn't completely hang and lockup the queues though? That doesn't seem right?
  14. We have the same issue for the past hour or so - I think the issue must be with the windows PWA server?
  15. We had the same start at the backend of last week prior to updating to 4.7.6 so I don't think it's linked to the update, just coincidental timing.
  16. When we go to upgrade to 4.7.6 we get stuck in a loop - after clicking upgrade: Version 4.7.6 of Invision Community is now available -> Continue Third Party Resource Check -> Continue Large Database Updates -> Continue Takes us back to Third Party Resource Check and then gets stuck in the same loop There is no way to proceed? Any ideas?
  17. Has there been a regression on this bug in 4.7.5? It was OK in 4.7.4 but we are not getting report notifications again since upgrading to 4.7.5?
  18. What was changed in your robots.txt file? We had a similar issue in Google this week but our robots.txt file hasn't changed at all but, it looks like the way google interprets has so all of a sudden, Google was believing it was being blocked. I think it's because we had a User-agent: * rule to set Crawl-delay: 1, because Google ignores the Crawl-delay part it was then skipping that line which meant the User-agent: * bit was then getting grouped with a rule further down blocking one particular bot so Google was assuming it was meant to be blocked as well. I've confirmed this behaviour in Googles robots.txt tester. I can only assume the way Google parses robots.txt files has changed recently and this behaviour has started occurring. It's likely to only affect people with a particular robots.txt format.
  19. I think I have found the issue that caused this - I don't know enough to know if it is something that could be sensitive - an underlying bug that once triggered could cause other peoples forums who are using ElasticSearch to generate GB's of error log files in the background automatically - how can I report this in a non-public way for investigation by IPB?
  20. We are having an issue with Elasticsearch - earlier our server ran out of disk space and when checking our core_log database had over 100GB of Elasticsearch errors in it. At some point the disk had got so full Elasticsearch had gone into a readonly mode but I don't know if that was the cause or symptom of the issue. We have now cleared the logs and made more space on the server so it has plenty and Elasticsearch is running OK again. We had a gap in the search index so decided to rebuild it in full but, we are still receiving GB's of errors in our logs, the same as the ones we were seeing before we fixed the space issue. The backtrace is this and several hundred occur every 5 minutes (presumably when the scheduled task runs): #0 /home/username/public_html/system/Content/Search/Elastic/Query.php(1238): IPS\_Log::log('Array\n(\n [qu...', 'elasticsearch') #1 /home/username/public_html/applications/core/sources/Stream/Subscription.php(145): IPS\Content\Search\Elastic\_Query->search(NULL, NULL, 1) #2 /home/username/public_html/applications/core/sources/Stream/Subscription.php(90): IPS\core\Stream\_Subscription->getContentForStream(Array) #3 /home/username/public_html/applications/core/tasks/dailyStreamSubscriptions.php(40): IPS\core\Stream\_Subscription::sendBatch('daily') #4 /home/username/public_html/system/Task/Task.php(367): IPS\core\tasks\_dailyStreamSubscriptions->IPS\core\tasks\{closure}() #5 /home/username/public_html/applications/core/tasks/dailyStreamSubscriptions.php(41): IPS\_Task->runUntilTimeout(Object(Closure)) #6 /home/username/public_html/system/Task/Task.php(266): IPS\core\tasks\_dailyStreamSubscriptions->execute() #7 /home/username/public_html/system/Task/Task.php(229): IPS\_Task->run() #8 /home/username/public_html/applications/core/interface/task/task.php(58): IPS\_Task->runAndLog() #9 {main} And this is the error coming back from Elasticsearch: Array ( [query] => Array ( [bool] => Array ( [must] => Array ( ) [must_not] => Array ( ) [filter] => Array ( [0] => Array ( [bool] => Array ( [should] => Array ( [0] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\core\Statuses\Status [1] => IPS\core\Statuses\Reply ) ) ) [1] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\forums\Topic\Post ) ) ) [2] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\gallery\Image [1] => IPS\gallery\Image\Comment [2] => IPS\gallery\Image\Review ) ) ) [3] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\gallery\Album\Item [1] => IPS\gallery\Album\Comment [2] => IPS\gallery\Album\Review ) ) ) [4] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\cms\Pages\PageItem ) ) ) [5] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\calendar\Event [1] => IPS\calendar\Event\Comment [2] => IPS\calendar\Event\Review ) ) ) [6] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\blog\Entry [1] => IPS\blog\Entry\Comment ) ) ) ) ) ) [1] => Array ( [bool] => Array ( [should] => Array ( [0] => Array ( [bool] => Array ( [must] => Array ( [0] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\core\Statuses\Status [1] => IPS\core\Statuses\Reply ) ) ) [1] => Array ( [term] => Array ( [index_is_last_comment] => 1 ) ) ) ) ) [1] => Array ( [bool] => Array ( [must] => Array ( [0] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\forums\Topic\Post ) ) ) [1] => Array ( [term] => Array ( [index_is_last_comment] => 1 ) ) ) ) ) [2] => Array ( [bool] => Array ( [must] => Array ( [0] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\gallery\Image [1] => IPS\gallery\Image\Comment [2] => IPS\gallery\Image\Review ) ) ) [1] => Array ( [term] => Array ( [index_is_last_comment] => 1 ) ) ) ) ) [3] => Array ( [bool] => Array ( [must] => Array ( [0] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\gallery\Album\Item [1] => IPS\gallery\Album\Comment [2] => IPS\gallery\Album\Review ) ) ) [1] => Array ( [term] => Array ( [index_is_last_comment] => 1 ) ) ) ) ) [4] => Array ( [bool] => Array ( [must] => Array ( [0] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\cms\Pages\PageItem ) ) ) [1] => Array ( [term] => Array ( [index_is_last_comment] => 1 ) ) ) ) ) [5] => Array ( [bool] => Array ( [must] => Array ( [0] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\cms\Records1 [1] => IPS\cms\Records\Comment1 [2] => IPS\cms\Records\Review1 ) ) ) [1] => Array ( [term] => Array ( [index_is_last_comment] => 1 ) ) ) ) ) [6] => Array ( [bool] => Array ( [must] => Array ( [0] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\cms\Records2 [1] => IPS\cms\Records\Comment2 [2] => IPS\cms\Records\Review2 ) ) ) [1] => Array ( [term] => Array ( [index_is_last_comment] => 1 ) ) ) ) ) [7] => Array ( [bool] => Array ( [must] => Array ( [0] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\calendar\Event [1] => IPS\calendar\Event\Comment [2] => IPS\calendar\Event\Review ) ) ) [1] => Array ( [term] => Array ( [index_is_last_comment] => 1 ) ) ) ) ) [8] => Array ( [bool] => Array ( [must] => Array ( [0] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\blog\Entry [1] => IPS\blog\Entry\Comment ) ) ) [1] => Array ( [term] => Array ( [index_is_last_comment] => 1 ) ) ) ) ) [9] => Array ( [bool] => Array ( [must] => Array ( [0] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\nexus\Package\Item [1] => IPS\nexus\Package\Review ) ) ) [1] => Array ( [term] => Array ( [index_is_last_comment] => 1 ) ) ) ) ) ) ) ) [2] => Array ( [term] => Array ( [index_item_author] => ) ) [3] => Array ( [range] => Array ( [index_date_created] => Array ( [gt] => 0 ) ) ) [4] => Array ( [terms] => Array ( [index_permissions] => Array ( [0] => 3 [1] => m123456 [2] => ca [3] => * ) ) ) [5] => Array ( [term] => Array ( [index_hidden] => 0 ) ) ) ) ) [sort] => Array ( [0] => Array ( [index_date_commented] => desc ) ) [from] => 0 [size] => 11 [error] => Array ( [root_cause] => Array ( [0] => Array ( [type] => illegal_argument_exception [reason] => field name is null or empty ) ) [type] => illegal_argument_exception [reason] => field name is null or empty ) ) Nothing has changed within the forum itself and no changes on the server side either that I am aware of. What is causing the huge amount of errors and how do I fix it please? Thanks, Grant
×
×
  • Create New...