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

5,971 profile views
  1. There are two new extensions for IPBWI for WordPress available (thanks to brickpicker.net) which are not available through IPS marketplace: IPBWI4WP – IPS User to WordPress Import IPBWI4WP – IP.pages to WordPress Import
  2. With IPBWI for WordPress v4, you'll get a perfect working Single Sign On experience. That means, you can connect all your forums (even IPS hosted) with your WordPress-Sites (even on completely different domains or servers). Please note, that IPS hosted board does not allow to get WordPress on that package, too. So you may need to install your blog(s) on a (sub)domain instead of a subdirectory of your forum's domain. Logincredentials and login status are shared between board(s) and WordPress sites. I'm working on several addons for IPBWI for WordPress v4 to allow deeper integration between WordPress and IP.board additionally to single sign on, but as IPBWI v4 API is included, you could build your own custom apps/plugins based on that API, too.
  3. Just to make it clear: you've made such a wonderful job with your theme and optimization of your IPS suite and I don't know a way right now to further improve that without breaking update compatibility, but I see there is a lot improvements required from IPS or by an application if possible, to allow maximizing Google pagespeed score. As this totally affects the search engine ranking, I see a high need for that and I hope I'll get time in future to solve this via update-save application or theme or both. This was a feature in IPBWI for WordPress v3 and I plan to re-develop and release that as extension for v4 this Fall or Winter.
  4. great I've checked your Google Pagespeed score and unfortunately, there is still a 65/90/76 score due to unoptimized images, delay in server response, missing browser caching settings for webfonts and most important, there are still renderblocking javascript and CSS ressources. I'm offering a 100/100/100 pagespeed score for my customers using WordPress and here's a small Sistrix chart showing how that impacts the search engine visibility: I don't see a way right now to reach a 100/100/100 pagespeed score in IPS on the current structure how themes are built for IPS.
  5. There seems to be something wrong with your DNS configuration, as I've got DNS lookup error on https://developers.google.com/speed/pagespeed/insights/ and few other sites, as well from my computer from Germany you site is not available. Maybe it's intended, but I don't think so. Nevertheless, glad to read you've reached a 97/100 pagespeed score with forums, that's awesome!
  6. Bob, that's totally awesome, big thanks!
  7. That feature has been offered for years with IPBWI for WordPress v3 and is on todo extension for IPBWI for WordPress v4. Will work just smooth. Unfortunately, getting something listed on wordpress.org requires it to be free and licensed to GPL - don't know at the moment which featureset could be delivered for free while getting users encouraged to purchase some kind of premium version.
  8. Just here some thoughts from me: Both, WordPress and IP.pages have advantages and disadvantages. You cannot say everything can be achieved with both softwares, as the effort to reach specific targets is completely different in quality and quantity. Currently, I don't see a way to optimize IP.board or pages to reach a 100% pagespeed, even with a custom theme due to the way, how JS and CSS is loaded in frontend. Some say WordPress is spaghetti code and that was true in the past, but nowadways, you can build an enterprise website with 100% pagespeed, perfect caching and maximum speed and security without breaking update compatibility in WordPress. Custom websites can be build with 25% effort and doubled quality compared to 4-5 years ago. IP.pages is intended to fulfill a niche and to do that as perfect as possible. IP.pages never will be comparable with WordPress. IP.pages will do a job and it will do the job just perfect, but there are website owners out there with a need to get the possibilities of WordPress plus IP.board. IP.pages will never fulfill even 1% of the functional needs of these website owners and therefor isn't an option at all. Same for IP.nexus, IP.downloads, IP.gallery etc.: All these are made for the IPS cosmos, based on a monolith concept, IP.core. That's great for thousands of IPS customers, but to make it clear: I assume there are more activate developers for WordPress than customers for IPS. IPS never can compete with that amount of code developed daily for WordPress. Yeah, many WordPress plugins are just faeces, but there are also many out there with enterprise quality for prices like 39 USD - thanks to the popularity and big userbase. Finally, another number: There are about 45.500 plugins listed on WordPress.org, plus about 4.500 on Envato. Additionally, some enterprise plugins are sold by their own websites, like WooCommerce, WP Rocket etc. In 9 of 10 cases, if a website owner needs a feature for their wordpress website, it's already done by third party for a fair price.
  9. I've started using IPB since v2. Remember? What a shiny, polished software Since v2, there was a long run until v4.1 we have today. From a developer standpoint, I can say that IPS has the best community software on market but unfortunately with one of the smallest audience for addon developers. This small audience actually has disadvantages, as there is a market for several features, but this market is too small to monetarize developing effort to fulfill needs. We are talking about initial development effort up to hundreds of hours maintenance effort when IPS decides to break backward compatibility new free features to give customers a benefit for renewals maintenance for new features support when wild bugs occur or a customer fails with installation / configuration Many customers expect a bunch of features for initial release of an addon, but don't allow the author to grow on purchases and reinvest into new features step-by-step. That's why we have so much small extensions without any grow, unsolved bugs and bad support - a developer cannot afford best premium support for 3x 10€ purchases. Yearly IPS license renewal costs are higher than this. I'm quite sure that "small audience handbrake" was the original intention of @RPG-support. I've reviewed the translation packages he is offering and I understand these high prices for the qualitiy he offers. Just imagine the audience would be 10-100 times bigger, the prices for addons could be reduced by half for sure with same or even higher quality. Apart from the value of actual addons and their prices, the amount of addons should increase to allow a bigger audience consider using IPS and paying the entrance fee. I've build several plugins for WordPress/WooCommerce, like a payment plugin and an order export plugin and built customer's sites based on WordPress. It just makes sense using that CMS as it allows to fulfill customer's desire with a very small budget while allowing to grow with the customer and replace scrap free plugins with custom code or premium paid plugins. Most of the WordPress addons actually are crap, but for example, an addon like IP.pages would be sorted into the "semi-sized well done"-plugins category if built for WordPress. So how could we help IPS to grow and how could IPS support community doing this? What could IPS customers do: if there is a common desire, IPS users should just hire developers out here for a reasonable price. Give professional third parties money and you'll give them a jump start into developing for IPS eco system. Don't think cheap. You get what you paid for. If you want a custom feature or a premium addon, you should be able pay what it costs and not what you think it's the value. If your business model does not allow paying high prices for high quality, don't complain about that, change your business model. What could Third Party Devs do: Be reliable. Show the world that your customers can count on you. They want to save time, so show that you are a time saver. Give proper instructions on how to use your extension, try to be better in documentation than IPS. What could IPS do: Worship your Third Party Devs. Currently, we have no achievement program, no trusted seal, no cross-marketing, no competitions, no incentives, no discounts, no chat pool with developers, no proper documentation, no guides for the entire framework mechanics etc. Instead of starting to worship a few trustworthy developers, currently IPS is worshipping none of the third party developers. There is absolutely no encouragement from IPS to motivate new or existing third party devs to contribute. Increase social media activities: Amount of followers is too small to allow you some marketing with impact there. You are just not present and it feels it's not important for you that you've got followed. How could you increase attention for new third party addons when there is rarely attention for your own posts outside IPS ecosystem? I understand that IPS software suite is intended to unleash it's full power when combined together. That could have been the reason why you want to avoid to release a part for free and open source to get more attention and a bigger audience out there. But that could be a chance: You may want to consider developing some product which would have a need on free market, but would give new users awareness about your portfolio. To make it clear: I am very happy with the marketplace being not available for non-license holders. An open marketplace or directory makes sense for an open software, but not for an enterprise solution. But I just want to show, that it's wrong to say: "If you don't want to pay for enterprise, just go to the humble free softwares out there, like WordPress". I know WordPress. I've customers with 4-5 digits yearly budgets, running very good on WordPress and love to use that CMS from prototype to enterprise solutions - all possible with WordPress. The disadvantage in IP.board is, there is no cheap prototyping possible. You can't just start with a new project and a small budget and a couple of free plugins and see how it goes and if it's successful, re-invest earnings. There is no extrinsic motivation right now to develop addons for free for IPS ecosystem. Amount of customization orders is too low to live from that, reputation has too small impact and it's a mess to invest weeks and weeks to get really known with all framework possibilities without proper documentation. More worse: Even non-free addons will not fully pay the rent. While in WordPress ecosystem, startups grow and venture capitals invest while I'm writing this, there is a deep silence when comparing to IPS. WordPress just have bought Woothemes because of their famous WooCommerce addon. Again: an open source software company has just bought another open source company which has built a famous addon. Wow. And now, honestly, we all need us to ask, why this could not happen within IPS ecosystem. Sorry for the long post, here's a potato smashing your car-analogies.
  10. That will be released as addon for IPBWI for WordPress v4. I know how to do that (I've build that for v3 before) and it will work great Before that release, there are some other minor features for IPBWI for WordPress core which have higher priority right now.
  11. I totally agree, that bugfixing on DEV environments should be encouraged and not declined. IPS cannot provide bugfree software (no one can, to be honest), so it should be allowed for customers to test and submit bugs prior roll-out on their live-systems. I've had a similar experience, where update from v3.4 to 4.x failed on DEV, submitted a ticket and got a negative response. Gladly I was able to fix that bug myself (baseurl was not set upon upgrade process), but it's not fair that IPS insists on providing support only, when a bug occurs on live. They are not asking whether it's the same server as live or a humble local WAMP, they just refuse. Regarding the Third Party Developer Support: I'd love if IPS could finish technical documentation first, to allow third-party developers to build stable and robust apps without jumping between hundreds of sourcefiles to understand the process of a specific feature and how to influence. Right now, IPS seems to follow the credo "this code was hard to write, it should be hard to understand". e.g. price tag auf my plugins could have been 50% off, if I've had a chance to reduce time for investigation. Not every app developer will go the extra mile to be able to release a polished and well tested third party application for IPS. I totally understand that not everything we wish is possible right now. AFAIK, community market has been decreased since success of facebook. While IPS is the best community suite on market (hell yeah!), I don't think IPS could make the same investments like WordPress to cultivate user generated content or handle a beta test with thousands of (possibly doubled) bug reports as well as motivate reliable volunteers to contribute for free from home desk just for some kind of glory. Finally, would be great if IPS could create some kind of feedback system where customers can add and up vote entries which are on screen then for IPS management and be able to be considered - this would avoid some kind of "rageposts" like this one from CheersnGears which are reasonable, but could be avoidable through better customer relationship management.
  12. Good question, as this scenario was a deal-breaker in v3. With IPBWI for WordPress v4, different servers are no problem anymore. that's correct, but I'll answer all questions here and love to follow discussion here
  13. IPBWI for WordPress v4 is available now on
  14. Version 4.0.3


    With IPBWI for WordPress v4, you will get flawless Single Sign On. How does SSO work? IP.board brings a SSO API which allows to add several "slaves" as satellites to a "master" IP.board installation. This results in a robust single sign on solution allowing unlimited slaves even on completely different domains - same origin policy which normally breaks setting cookies for different domains has been bypassed here successfully. Requirements WordPress 4.5 or higher IPcore/IP.board 4.1 or higher PHP 5.5, PHP 5.6 & PHP 7 How does IPBWI for WordPress exactly work? Please see documentation for a description of each feature. Installation / Configuration unzip download package on your local harddrive copy folder ipbwi4wp to /wp-content/plugins/ active plugin in WordPress go to IPBWI4WP settings menu page follow further instructions there Additionally, the powerful IPBWI-API, which worths 89 $ and is included, allows you to develop powerful extensions by your own. Follow IPBWI IP.board WordPress SSO on Facebook and Twitter! There are extensions available on straightvisions.com store: IPBWI4WP – IPS User to WordPress Import IPBWI4WP – IP.pages to WordPress Import


  15. IPBWI for WordPress v4 SSO is working and if anyone is interested in beta testing, just contact me