• Content count

  • Joined

  • Last visited

About Alex

  • Rank
    Frequent Contributor
  • Birthday March 20

IPS Marketplace

  • Resources Contributor
    Total file submissions: 1

Recent Profile Visitors

111,130 profile views
  1. Very impressed with IPS Community Suite 4.0. Great job to everyone involved. :)

  2. I am of the opinion that it's up to you as a site owner to make sure you comply to local laws. If IP.Board implements this cookie law for example, what would stop some customers from another country demanding that their laws are adhered to? Things like this, and COPPA (which is another silly law) compliance are definitely up to the site owner :smile: Just do what the BBC and the majority of major UK sites I have seen use, put a small banner at the top that says along the lines of "By using this site you agree to us storing cookies, leave now if you do not wish to". IP.Board wouldn't have stored anything by that point.
  3. I'll look into that this weekend, but the passwords can only be synced if they manually log in to IP.Board or WordPress (in other words, they don't use the automatic SSO) - SSO itself won't transfer passwords due to them being unreadable as hashes. There's no reason to say why this won't work on 3.4.0 but I will be testing it with the new WordPress release this weekend and get back to you.
  4. Yes it is, though that specific change only applies to vBulletin conversions at this stage, we can roll it out to others with ease if requested but vBulletin is where we see the bulk of the very large forums coming from.
  5. Hello, You can setup the forums to how you wish before rolling out, however at roll out you will need to reconvert any area which has changed (so usually members, topics, posts, pms, and attachments.. in that order). You won't need to create a new install of IP.Board. You would also have to visit the recount and rebuild areas after your second conversion to make sure all the caches are up to date :)
  6. That's an issue with your server if the connection is timed out, nothing to do with the modification itself :-)
  7. The new converters are available for testing only. If you have a large forum, or you're converting and finding the converters are too slow please submit a ticket for my attention and I will send you the download so you can try out the new improvements. All being well they'll be available for everyone shortly :)
  8. Millipede, I'm sorry for your frustration, could you PM me the ticket ID please and I can look into what's happened here?
  9. Wolfie - where as you could recreate a bug tracker in IP.Content (as we have done), it was done to suit us better. If you want a bug tracker on your forums, Tracker is still being developed.
  10. I think you're reading way too much into a number which just gives a bit of credit to the contributors. You make a change to a language string, you get a 'commit' added to your account. People that have more have worked on more than one language pack. As for why yours isn't showing 7000 I don't know, but I don't think its the best use of anyones time to see why you don't have 7000 showing under your account? The language pack is complete, and you have credit on 99.9999999% of that pack, that's all that matters surely? :)
  11. An update has been pushed out to this hook: New in 1.3.0: SSO and Login Authentication is now separated. What does this mean? SSO is the part of the hook which automatically logs you in to the account if you are logged into WordPress, or vice versa. If you don't want this functionality, you can now turn this part off but still allow users to login via the login forms. 1.3.0 now fully supports the IP.Board 3.3 series. Changelog IP.Board 3.3 SQL error on installation fixed. Now supports IP.Board 3.3.3. SSO and Logins have been separated so you can turn one or the other off at any time, this fixes issues with sites on multiple domains. Change Display Name in IP.Board now fixed.
  12. With all due respect, I have been working on other things as well, and the bug you are reporting is hardly show stopping, it doesn't stop you being able to translate or download packs, it just marks a few strings as updated due to the symbols - on the grand scale of things I'd say that was a pretty low priority bug. I'll look at these, but these are all relatively minor problems.
  13. You visited but forgot to leave me a message :(

  14. Fixed. Fixed. Search is working for me - it may have been fixed by me sorting the other things out though. Not a bug, if someone comes along and updates all the translations we don't want peoples previous contributions to be forgotten about, seems wrong to remove them. Cannot reproduce. Fixed. Not too sure what you mean here, special characters seem to be displaying fine for me.
  15. Just to keep you updated on this, we are working on these issues you have pointed out and will let you know when the system is updated here. :)