Forum Replies Created
Bluehost is going to struggle to work with your network. Yes, there are many hosts that are very affordable, but remember, you get what you pay for.
With a pay-as-you-go service, the service is able to scale with you as your network grows. And while that does mean higher costs as your site gets more popular, it also means that if you are charging your customers, you are more able to afford those costs.
Of course, if you have a very successful network, then honestly, none of the existing managed hosts are going to really be able to help you, unless of course you are willing to spend at least $1000/month on them. At that point, you may be better off hiring someone to help you get setup with distributed and load balanced cloud hosting like AWS, Azure or Google Cloud.in reply to: closte.com vs Bluehost.com
@stef, I have found that if you are trying to access the signup flow as a logged in user that you get the error that you’ve reported.
I have reported the issue as well @arindo has added it as things to look into.
Thanks for considering it.
I love composer too. It really does make life easier. But I’ve run into the issues as well in the past creating some custom site plugins for clients. So now, I just add Gulp into my build pipeline to find/replace stuff in Composer dependencies.in reply to: List your plugin conflicts here? …
For taxes in the US, https://taxcloud.com/ offers free tax calculation (as long as you collect for all their listed states) or a small monthly fee otherwise. Makes calculation much easier if you must calculate based on where the user is.in reply to: Help with VAT and Taxes Support
Ultimo and ZeroBS CRM addon StripeSync conflict.
Both make use of the Strip Composer library with different major versions.
While composer is a great package manager for PHP, I wish more WordPress Devs would understand that they need to change any namespaces to avoid possible version conflicts. It does mean more work, but it avoids a ton of conflicts.
I just ran into this conflict about 2 days ago (only realized today where the conflict was).in reply to: List your plugin conflicts here? …