Leaderboard

No problem at all! Sorry if my tone came across as frustrated or irritated, I was just trying to be "to-the-point" and informative in as unbiased a way as possible, just presenting the facts and evidence I could find to support my case. I'm genuinely happy to answer any other questions or concerns you have, if any! *online hugs*

Warming up the beta forums. We've scheduled Beta 1 to start next Thursday, September 15th. We've had quite a few issues pop up with regard to the minPHP upgrade, and we're really close to having those all resolved. That's not to say we've caught everything. Being a major release, please consider 4.0 beta 1 more of an alpha, and do not under any circumstances run it in production. Looking forward to it!

I'd like to make a request for the ability to set a unique email subject for each service activated. Right now, if a client orders multiple services they receive each email with the same subject and it seems to be real easy for them to misplace them or not locate them for one reason or another (they seem to just delete them most of the time). When it happens, our work around is to copy and paste the info from the bcc email we're receiving but it makes things a bit less efficient. Example: Customer orders hosting, a domain and an SSL Subject for Hosting: (let us set this when we set the package email contents) Subject for Domain: (let us set this when we set the package email contents) Subject for SSL: (let us set this when we set the package email contents) This would also allow them to search their inbox a bit better as well. I think we all know that a lot of people don't keep a very neat inbox! What is the reason behind the 'New Service Activated' email? It seems like an extra, un needed step / feature to me but I'm sure there was a good reason for it. Sort of a 2nd feature but related: Maybe make a copy of each welcome email available for download within their account.

There is an "Export" option, you can export the theme to a file, re-import it with a different name and then edit it to add your logo. We could probably make that more clear.

okay thanks

Hi Timnboys, I'll address your points in order. Most of the pages on the website head to a 404 because I've been working on other products rather than my own company website. I don't get any business through the website at the moment, so it's been left in a bit of a state of "half-doneness" where other projects have taken priority. There's enough there for people to get in touch if they require but not enough to serve as a functional company website. I can understand why that looks odd. The domain was registered in 2014 because prior to this I did web development under a different name (Hash Development) - I'm sure you could lookup historical WHOIS records to show there was a domain registered around that time (www.hashdevelopment.com). After this, I did some work under my own name, before moving to the Cogative brand around 2014. Earlier this year I registered as a company in the UK (this is important later). The WHOIS data listed a Canadian address because contact privacy was enabled. This is a feature available through many domain registrars which allows you to register a domain without listing your residential address. In an effort to put your concerns to rest, I've disabled this and the WHOIS records now list the company's registered office in the UK. You can see this here: https://who.is/whois/cogative.com, you'll also see the enverido domain is registered under the same address: https://who.is/whois/enverido.com You are correct, the Cogative website is based on Wordpress. This is because there wasn't any benefit to developing a custom CMS for it when Wordpress was readily available to install - this comes back again to the point that there's no business coming through that website at the moment. It's a standard Wordpress install with a Bootstrap 3 theme on top. I can find the base template for you if needed, however I customised the CSS and some layouts to give the site a more unique style. Finally, to alleviate any further doubts you can find the UK company registration at Companies House here: https://beta.companieshouse.gov.uk/company/SC524151 - I'm not sure where you're based, but in the UK all companies must be registered through Companies House with correct and up-to-date information. This is done through what's called a "Confirmation statement" which must be submitted once per year. As you can see, the company was officially incorporated on the 13th January 2016 (as I alluded to earlier). The gap between the domain registration and company incorporation was due to the business being "something on the side" until the start of this year, where it started to play a larger role and it became important to register the company. In addition to the genuine company registration, all of our payments are handled through Stripe. The only payment information that we store is the last 4 digits of your card, your card type (eg: VISA, American Express, etc), and a Stripe customer ID. Any actual payment information (full 16 digit card number, expiry date, CVC code, cardholder name) is stored by Stripe. If you take a look at the source of the subscription page in enverido, you can see we use data-stripe attributes on form inputs specifically so that this information never passes through our servers - take a look at Stripe.js (https://stripe.com/docs/stripe.js?) if you want to know more about this. This allows us to be PCI-DSS compliant, and hopefully lets you sit safe in the knowledge that your payment information is stored securely by a recognised vendor. If worst comes to worst, you could even have Stripe refund the full amount of any payment made to enverido. I hope this alleviates your concerns. Please let me know any more questions you might have and I'll try my best to clear any misunderstandings up. If this really is a scam, I hope you can see how elaborate it would have to be! Further to this, you are free to try out the homebrew (free) plan without providing any payment information to ensure that enverido really is a functional product. Once again, I hope this clears up any misunderstanding, but please feel free to ask any other questions.

Security Report finished look here for the pdf: Link to Report https://twitter.com/pwnsdx/status/775897491367661568 ^ hash

Take a look at the very first version of our PHP library on GitHub. There are installation instructions on there, too. We'll be implementing more functionality over the next couple of days however licence verification is in there. Tomorrow we'll be tidying it up a bit by using the Verifier class, but it's a start! We'll start adding updates on our Twitter feed so we don't spam this thread too much.

Ah! I didn't select a non-default theme, and was trying to find a way to use Blesta Blue theme and change the logo. Thanks.

How much work waiting me!!! i need update all my plugins and modules .... Anyone know where i can buy more time for my day ? 24 hours is not enough for me !!!!

Plugins and other extensions should be backwards compatible yes.. but you should *test* this. We've run into some issues where our plugins were not working properly and have had to make adjustments to the minPHP bridge. As Mike mentioned, you may want to update your buttons in your plugins to use the new Bootstrap ones, but if you don't they should still work. Test, test, test, everything you can think of. It's possible we missed something, and being a major release, this version requires extra scrutiny.

Everything, really, since essentially everything has been updated. i.e. submit every form with good and bad data perform every action (including those in extensions) check for anything out of the ordinary like blank white pages, or pages with errors upgrade from version 3 to 4 create a new installation of v4 perform migrations from v2.5/whmcs to v4 check for obvious (or not so obvious) page styling issues see if anything comes across confusing that you think can be improved ensure current functionality still works try out the Mass Mailer plugin A dev system would be perfect, but where would you be importing data from? Not real data from a production environment, correct? Sometimes people insist to me that they want to test changes in a dev environment where the data mirrors what is on the production server. It sounds like a simple and convenient way to test what is and what will be, for comparison. They'll just disable emails from being sent and disable payments from going through in order to be sure real customers do not receive emails or get charged from the dev environment while they are testing it. However, this is a horrible, horrible, horrible idea for numerous reasons. Not only does it limit what you can test (e.g. can't test sending emails or making payments), but bugs may exist that send emails, make payments, etc., even when disabled. All data in a test/dev environment must be test data. I hope that's the intent of everyone that will be trying out the beta.

Your profile image looks delicious.