Jump to content



  • Posts

  • Joined

  • Last visited

About Nils

Recent Profile Visitors

10,653 profile views

Nils's Achievements

  1. The upgrade to version 4 a few years ago left me in a bad situation: I had been running IP.Board 3 for many years and have made a lot of customizations to it. Unfortunately this meant that upgrading to version 4 would have been a huge effort. There are so many backwards-incompatible changes between v3 and v4 that I would have to rewrite many things from scratch. My forums are just a small side project at this point so I cannot justify the time investment required to do this. And thus I have unfortunately gotten stuck running version 3.4.9 for the last few years. I know the 3.4.X branch isn't officially supported anymore but I was wondering - is there anybody else here that is stuck in a similar situation? Are there any resources available for us? In particular, I have two major questions: Have any security issues been discovered since the last official update? Are there any fixes? Has anybody explored how to make IP.Board 3.4.9 run on PHP7? I found a post online saying that PHP7 was not supported but I don't know whether that means it just hasn't been tested or whether there are any practical problems. I would be very thankful for any pointers! I am comfortable making changes to the code base myself if I have to.
  2. As one of the people still stuck on 3.4.9 for the foreseeable future I recently made some changes to the recaptcha.php plugin to update it to Google's new v2 API. I hope this will help alleviate the recently uptick in spam bots a bit, and will also ensure that reCAPTCHA continues to work after the old API is shut down in March. This was done in a bit of a rush so I can't guarantee that my code is perfect or free of bugs (so no warranty etc), but I thought I'd share my changes anyway. Maybe someone else can make use of this too! Simply upload the attached file to ips_kernel/classCaptchaPlugin replacing the old recaptcha.php (maybe make a backup first). Then, sign up for v2 API keys here: https://www.google.com/recaptcha/admin and copy the "site key" into the "public key" field and the "secret key" into the "private key" field in the Spam Prevention settings in the Admin CP. Note that other reCAPTCHA settings (language/theme) are no longer in use, but at least the language should now be auto-detected anyway. I haven't tested this extensively, but it seems to work fine in my installation! recaptcha.php
  3. Is there still no fix for the member list problem?
  4. Imagine the user has been reported before. Now if you report him again, the original report will be bumped with the new report message. But if you don't read very closely, you might not actually notice the new message, so you will get confused about why this old report is showing up again. Also, when people comment on this report it becomes very hard to see which comments are talking about the new report and which ones are talking about the old one. Depending on the amount of discussion before one might even have to browse through several pages of comments to find it. And now imagine the chaos if this happens multiple times for a single user. I am speaking from experience here...
  5. Would it be possible to add a separate reporting system for status updates (like for posts, blogs and so on)? At the moment the only way to report these is by reporting the user, which gets very confusing over time, since when there are multiple status update reports for a user they all end up getting combined into one giant report thread.
  6. I am not talking about diff reports or anything like that. Having the list of fixed bugs but with some priorities assigned would already be a lot more helpful. Ideally new features would also get tracked through the bug tracker and would show up in that list as well.
  7. For the templates, yes, but not for the software itself.
  8. I would just like to bring this topic back, as I still think a change log would be essential. An unsorted 7-page list of bug reports just doesn't cut it. It doesn't tell me what is important and what is just a minor fix, it doesn't tell me what the breaking changes are, it doesn't tell me where the known issues lie and it doesn't tell me what areas have been changed at all. So instead I have to either install the update and hope for the best or manually diff the files to see what has been changed, both of which I would not call good solutions. I really don't understand why this is such a problem.
  9. So what is the verdict on this now? Will 3.4.2 include an improved non-RTE editor? If not, will a later version? And what about making the editor pluggable in general?
  10. I don't think Cloudflare is the problem here. The reason that IPS activated Cloudflare in the first place was probably that they were being targeted by DDoS attacks that they could not cope with on their own. So the site would probably be down a lot more without it...
  11. Oh, okay. Maybe that should be labelled "Direct Chats" or something like that then... Any news on a proper ignore feature?
  12. I just noticed that there actually is an option "Chats" in the ignore settings: http://community.invisionpower.com/index.php?app=core&module=usercp&tab=core&area=ignoredusers Does this mean this feature has now been implemented??
  13. Don't be fooled, the editor in 3.3.4 is also far from perfect, to the point where we ended up moving some of our larger posts into an external Wiki because there were so many formatting issues. I don't know what the editor in 3.2 is like, but it might make sense to wait...
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy