IPBWI.com Matthias Reuter

  • Content count

  • Joined

  • Last visited

1 Follower

About IPBWI.com Matthias Reuter

  • Rank

Contact Methods

IPS Marketplace

  • Resources Contributor
    Total file submissions: 6

Profile Information

  • Gender

Recent Profile Visitors

6,282 profile views
  1. correct
  2. That feature is planned as addon in 2016, but I cannot give an ETA for that.
  3. You may take a look here: https://invisionpower.com/third-party/providers/ From my opinion as full time developer / freelancer, most customization requests have a lack of budget compared to the effort. I do not pitch in the customization request forum, as most requests are in pocket money dimensions. While IPS 4 suite has an enterprise-sized framework and a lack of developer documentation, proper customizations or app development will require more work than most clients can afford.
  4. Terranigma / SNES
  5. 15 hours since and still everything fine
  6. yep, that annoying bug is gone now, too
  7. I've fixed that and made a full import again. Let's see if my other fix is successful now.
  8. There could have been a bug in the following situation: user logins in IPB user account already exists in WP, but not in all blogs of your WPMU site network user account will be added to all blogs, but with default "subscriber" role. if user already exists in a blog, user rolle was overwritten I've implemented a check in the case described above now to avoid overriding the role upon login when a user already exists in a blog while still adding user to all other blogs as subscriber as intended. If you start a re-import now, the issue should be gone.
  9. let's focus on Alpinemaps: I've ran a test import for that user only (to speed that up a little) and moderator group has been set as role successfully. Please give me a note once this member's role has changed back to subscriber again and I'll investigate further.
  10. checking it right now. Can you send me an email with new login credentials for WordPress FTP? Old ones are not valid anymore.
  11. if you can research which contributor account is affected by this issue, I could make some investigations to get it reproduced get it localized get it fixed
  12. There is only one situation when a role is set in WP by IPBWI and that's when a new account is gonna be created in file sso_by_ipb.php within method register so this shouldn't be the reason. As far as I remember, you are using a nginx setup which caches PHP output. This could result in the situation the you won't see the most recent data right after import and need to wait until this cache has been flushed again by nginx. This could be the reason for the different counts.
  13. vs. Seems re-import is actually working? that's a good news and means - at current state of information - there is no major bug with group mapping upon re-import as both of us thought? real-time user group synchronization is far more complex. We are talking about 5000 € effort if you would want that feature by two weeks. re-import by group would result in 1200 € effort. While I'll wait for some sales on my user import script before adding new free features, the real-time user group synchronization feature will be released as separate addon later this year. if this issue occurs again, we will have put on our investigator hats to fix it, but right now I have no idea, too. Chances are big that there were conflicts upon import for these 104. With such a big user base, there could be corrupted member accounts. Nevertheless, my user import script has some type of debugging log printed upon import. In future versions I'll try to improve it further to get a better overview on those failed import attempts.
  14. last weeks: 120 € / hour since today upon withdrawal: nothing, as I've time now again for free premium support for you.
  15. following are my thoughts about your feedback in your last post: Are, but not were, as far as I know. You've changed that after initial import In most cases, this plugin will be used only once to bulk import all members and go live. If there are issues, prior imported members will be wiped and another, fresh import will be started. That will work for most buyers of this plugin. The plugin has no magic hook changing the userroles of existing members without any action by you. You've started the import again without wiping member accounts in WordPress (a "re-import") and there could be a bug left. As I said, the re-import feature was never ordered nor paid by you. If the plugin is worthless for you without that feature, you should pay for it or bring some patience. Some business trips require that I totally focus on them for that time. We have no service-level-agreement (which would be quite expensive), so I was not able to bind a programmer from my network to fulfill support for you. In your situation, I would ask how much it would cost to get premium support and bugfixing for a free, but not yet supported extra-feature. They are rock-solid. You are complaining about something that is not part of the official featureset. It's usual to deliver optional features in a beta state along with a stable product as long as they do not affect the core product - and in this case they actually do not.