Yup, just go for it but keep in mind frustrated customers that won’t understand what they need on their servers, so make sure you are very very clear about requirements.
On the bright side, i think latest version of centos has phalcon in epel or remi repo so owners of such vps will simply issue a yum install php-phalcon i believe and everything will be installed for them. And if centos has it, them most likely ubuntu/debian and derivates have it too.
I am pretty sure that this is not allowed. All files must be readable and work on a standard shared hosting. Both is not the case with this framework.
There is absolutely no reason why it should be not allowed. Phalcon is implemented as a php extension like GD or IMAP or whatever else and this guy code will still be php in php files, accessing classes defined by the above extension like you access getimagesize() or imap_open() from the GD/IMAP extensions.
The only thing is that, well, the target server must have that extension enabled, so good luck with setting that up, but other than that, no problem whatsoever, what now, don’t allow php project that require mcrypt and mbstring in order to work? come on
FinalDestiny saidDon’t worry about it, they’re already working on it. Simply add your full name and address, and everything will be fine.
And basically they can’t ask for our info till 1st of January since many of us will be on vacation / without internet connection. So I’m really curious what you’ll add on the invoice.
If this is anyhow true, it’s soooo twisted, more than i am…
natman saidEnvato Market operates on a platform model where authors are acting as seller directly to the buyer.
Envato Market operates on a platform model where authors are acting as seller directly to the buyer. This is complicated by the fact that for VAT purposes only, and as of January 1st, Envato assumes the responsibility for managing, collecting and remitting VAT. Put another way, for VAT purposes only, Envato acts in the capacity of supplier.
Why are you keep saying this ?
Yeah, me neither, but it can be expanded in such way that ratings wouldn’t be a weapon against authors.
One can wish…
We should be able to rate customers back as well after they rate us and give reasons why we rated the way we rated. The rates for customers should be public visible by everyone so that future customers can see why certain customer gave a low rating to an author product and what author has to say about this.
This will most probably put an end to abusive ratings.
Why would you ever beg for a rating?