Quote:
Originally Posted by AJHall
It's always interesting when someone with a low post claims to have their own CMS coming out soon and wants to trash my product. Your attempt wasn't bad except that you are entirely wrong in nearly everything you just posted.
To clarify:
We have had no reports of content processing slowly or this being an issue. The moment customers start to complain about this or we are aware of an issue in this area we will address it and make improvements just as we have with every other performance complaint since 2006. 
As far as server resources, we make use of multiple levels of caching for performance. Elevated X power thousands of sites including a number of big brands and large cash programs. Many of our small to medium-size customers are on budget servers ($99-250 per month being spent on hosting) and the majority of our users do not require use of multiple servers.
You said install docs are poor. Correction - There are no install docs as our staff performs 100% of the installations and setup of the CMS.
There's no need for a customer to install or reinstall any server modules - ever. We recommend managed hosting and work with several leading adult hosting providers. We suggest that our customers use reputable web hosts familiar with the required modules, all of which are common. Over the years, we have encountered situations a handful of times where someone has the level of difficulty with modules that you describe. Usually this happens when a server tech or sysadmin is unfamiliar or inexperienced. Thankfully when this happens and a tech struggles to this degree we have a list of A-tier hosting providers on hand who can step in and have things working in a matter of minutes.
Elevated X DOES NOT require Wowza although we do support Wowza streaming and many of our customers are very happy with it.
Publishing large amounts of content apparently isn't too time consuming as we have an awful lot of customers with massive sites and networks that have many thousands of content sets.
Switching to Smarty templates in 2009 has been a good thing for us, our users and the growing list of designers who provide services for Elevated X customers 
AJ |
Yeah, I tend to read and keep my mouth shut which is why my post count is low. Funny, when I was posting earlier as I finished I said to myself, "I wonder how long it will take AJ to show up and tell me I'm full of shit"?
You DO have reports of photo rendering performance issues, I filed the support ticket on it so I would know. Your lead dev told us a solution would be out two weeks ago, now we're told no estimate on a fix. We've just shut the damn thing off and plan to render the screen caps elsewhere or revisit them once a fix is made.
Once content is ingested, or if you have a small site without a lot of content I'm sure that 99 dollar server will work just fine (heh). Then again, if you're hosting your adult site on a budget box, VPS or shared hosting account I kind of doubt your licensing ElfX but whatever.
Your install service requires a slew of requisite software to be installed - that's what I'm referring to as being poorly documented. It's pretty shitty to toss around comments about server admin's experience levels when you don't provide them with enough information.
If your software requires a specific version of ffmpeg, for example and it's not the current, "release" version and it MUST be installed from source (not GIT or SVN) then you should probably tell people that up front. Not doing so is considered crap / no documentation, IMO. When one of your install techs gives me a laundry list of changes that need to be made the first thing that comes to mind is "if you knew all this why didn't you just tell us up front rather than add 3 days delay while we uninstall / reinstall everything using the "correct" versions / methods and then have to wait for our turn in line again"? The difference between your "A Tier" providers and everyone else is they've gone through it before and know all that undocumented info. But hey, blame the end users, it works.
As for large content ingestion - your big clients use modified installs with multiple encoding servers. I was shown a tech doc on this that really has zero info on how to do it and mainly makes clear that if you work it out you become "unsupported". Obviously if I were say, Playboy and wanted to do something like this I'm sure my support would continue without issues vs. me doing it and then finding any issue I run into will be blamed on the multi server mod and receive zero support. Just my gut feeling on how that would go....
Smarty templates are great for one thing. When the hack of the week comes up it's always fun to watch the blame shifting game between the app devs and the smarty devs. I'm aware of one security hole that's been there for two years so far and still isn't fixed because neither side will budge on who should be fixing it. Fun, fun.
In all honesty I don't have any plans to do a new CMS. I just knew it would wind you up.
Someday though, someone is going to take a proven, robust CMS from Enterprise and modify it to do adult content. It really wouldn't take much to do it and the quality of coding, standards compliance, etc is like ET landing in 500 B.C. vs. the current state of the art within the industry.