Orbit Storm:
However, immediately disqualifying support requests based on the host just seems silly to me.
I can appreciate that it may appear that way, but that really isn't the case.
Orbit Storm:
GoDaddy clearly has its quirks (as I'm finding out), but they're also a quality host for a bargain.
Forgive me, but not once have I ever seen or heard 'Godaddy' and 'quality host' being used in the same sentence before.
Orbit Storm:
But feeling like I'm not "good enough" for support, solely because I opted for a cheaper route financially, already has me cringing at the idea of asking for future support here.
It isn't you, and it isn't personal. Please accept my apologies if I have made you feel this way.
I'll also apologise on behalf of the zencart team for their current lack of input too. It really is highly unusual. When I said 'many around here will ignore support requests from GD customers I wasn't referring to the zencart team themselves, but moreso those of us that are little more than experienced users.
In my experience it has been rare for the zen team to let any support query go unanswered ... even if the answer turns out to be no more useful than mine.
Orbit Storm:
Again, this could be another instance of perception vs. meaning,
I'm sure it is.
I don't think some of my comm[quote=Orbit Storm;1111371]ents have really helped in this perception either.
Orbit Storm:
but as with you, I've definitely taken it as my account being stamped as "unwelcome". If that's the type of business model the Zen Cart team is willing to condone on their support forums, it isn't any wonder Zen Cart has more negative than positive reviews.
This isn't a jab at you, because if this is the "way it is" around here, clearly that custom started long before you.
I honestly don't know why the support team haven't responded yet. As stated previously, your issue does appear to be rather unique, so I can still only assume that someone is taking a more in-depth look for you, and this will take a little longer than normal.
Orbit Storm:
I chose not to divulge the name due to not wanting to "advertise", but it really isn't an advertisement as I haven't used it yet.
The software I'm referring to is osCommerce. As I mentioned previously, they have hundreds (potentially thousands, but I didn't read that far) of positive reviews - ranging from user-friendly to virtually bug free.
You probably aren't aware of this, but ZenCart was actually derived from OsCommerce, and if you do a little more research you'll find there are far more people that migrate from OsCommerce to ZenCart than the other way. The reason is, OsCommerce are very poor/sluggish with updates (even security fixes) and the support is very poor in comparison to ZenCart, and if the users of my ozpost shipping module is anything to go by, it has less than 1/10th of the number of active users.
Personally I think you would be wasting your time with this one.. I'd suggest you take a look at PrestaShop, OpenCart or VirtueMart instead, not that their support is any better, but simply because they don't share the same code as ZenCart, so you probably won't run into the same kind of issues.
Orbit Storm:
Problem with that is, the issue isn't on GoDaddy's end this time. Zen Cart removed the options themselves, thereby leaving users no option to ensure cURL proxy is disabled.
This is where the real mystery lies, at least as far as I'm concerned, because I know for a fact that ZenCart requires cURL for several of its features (including my own module).
The need for cURL proxy was something that was needed when using GoDaddy, but very few other servers (at least it was a couple of years back).
The code snippets I provided earlier (from the zencart installation scripts) defaults to having the proxy disabled, which is going to be correct for most users (except GoDaddy)
From what you have told us GoDaddy no longer require the use of the cURL proxy, which brings them back in line with most other servers.
Also as I stated very earlier in this thread, it would be foolish for the zencart team to force the proxy to be enabled, because to do so would almost certainly cause problems for pretty much everyone.
I can't find anything anywhere that would cause your installation to have the proxy enabled with the options to disable it being removed, so on this basis, your problem really does appear to be unique and without explanation.
Orbit Storm:
It's simple: cURL proxy is still enabled, and I'm unable to disable it via the Admin panel, because the options were removed.
Regardless of all else, this is wrong It would/should never be this way because it WILL cause problems, not just for you, but for pretty much everyone.
Orbit Storm:
Belittle GoDaddy all you like, but that won't solve the problem that is definitively a result of Zen Cart's actions.
I'm not as convinced as you are. I've looked at the zencart code from the V1.5 distribution files and I've posted a copy of the relevent parts into this thread for all to see and inspect, and this code clearly shows that the default setting is for the cURL proxy to be disabled. Therefore the only conclusion that I can come to is that the installation scripts being used by GoDaddy are NOT the same as those provided by the zencart developers, ergo it isn't a result of ZenCarts actions at all.
I'm not going to say that the GoDaddy made the changes either, they probably use another 3rd party installer package (such as Fantastico), so this could be a case where the cause is neither with ZenCart or GoDaddy, but the 3rd party installer.
Actually this is currently about the only logical thing that makes sense.
Orbit Storm:
And again, as mentioned previously, I don't have the luxury of spending wildly for extra resources I simply don't need. GoDaddy is a low-budget option, and I'll be sticking with them.
You probably won't like what I'm going to suggest, but have you considered doing a manual installation of zencart using the official distribution files? I'll wager that if you do, the problem will go away.
Orbit Storm:
To me, it suggests that you have had more hands-on experience with the thousands of support requests here, and that if you're unable to think of a possible solution, then it's unlikely there are many others within the community who would either.
It doesn't really work that way (I wish it did). I really am struggling for an answer/explanation. I'm not like many others that will simply dismiss the problem because of the host you are using, because in this case it really doesn't seem to be that simple.
There is a mystery to be solved. There is something wrong with your installation. The default zencart install scripts appear to be doing what they should, GoDaddy insist they haven't messed with these scripts, the scripts don't modify themselves, so the only possible conclusion is that some other party has made the changes.
Actually I can think of one other possible cause, but it would be so remote and unlikely that it probably isn't even worth mentioning, but it is possible there was a glitch of some sort with the mySQL server at the exact time that you did your installation and this glitch prevented the database from being populated with the cURL settings.
...........
Hmmm.... Just for grins you could try going to the zencart tools/install SQL patches and running the following query
INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, set_function, date_added) VALUES ('cURL Proxy Status', 'CURL_PROXY_REQUIRED', 'False', 'Does your host require that you use a proxy for cURL communication?', 6, '50', 'zen_cfg_select_option(array(\'True\', \'False\'), ', now());
INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('cURL Proxy Address', 'CURL_PROXY_SERVER_DETAILS', '', 'If you have a hosting service that requires use of a proxy to talk to external sites via cURL, enter their proxy address here.
format: address:port
ie: 127.0.0.1:3128', 6, 51, NULL, now(), NULL, NULL);
```NOTE: If your database tables have a 'prefix' then you'll need to edit the two places that read "INSERT INTO configuration"
so they match your table names, eg "INSERT INTO zen_configuration" (assuming your table prefix is 'zen_')
About the worst thing that will happen is it'll produce some kind of error message. If you run it a second time the error will/should be 'cannot insert .... because it already exists'
Since there is still no other input to this thread I don't think you have anything to lose. You can't/won't make anything any worse.
Good luck.
Rod
