Jump to content

So apparently according to IPS support...


Recommended Posts

Posted

I do not know how to put together a windows, apache, with php and mysql to work with 4.0 ; 

I have been running IP3.x for a few years now, been working flawlessly. Decided to do the 402 release upgrade, that's when I start having problems. HTTPS stopped showing CSS, so all I saw was text. I was getting weird errors in commerce that were only on certain clients. And the background rebuild/postupgrade tasks were frozen. When I talked to support via ticket, they claimed that not only my database was then corrupt, that my installation was also bad too. Even though before upgrade, it gave me all greenlights, and even during it said everything was okay.

 

Was wondering if anyone had any tips or something?

 

EDIT: 

 

  • What is the environment you are running your website from?
    • Windows 2012 R2 ; Apache Apache/2.4.10 (Win32) OpenSSL/1.0.1h  ; PHP 5.4.30-Win32-VC9-x86 ; 
  • IPB Hosting / Shared hosting / VPS / Cloud / Dedicated Server?
    • Dedicated Server
  • If VPS/Cloud/Dedi, what are your cpu, ram and disk availability?
    • Dedicated, System-- Intel Xeon E3-1270 (Sandy Bridge 3.4ghz) 1 processor 4 core. 32gb ram, 2tb hdd, 160gbssd ; 
    • Memory_limit 128M
Posted

Revert your forums from a backup back to 3.4.7 then wait for version 4.1 to come out. Those of us who have been around for a while know from experience never to upgrade to the new version when it comes out. Wait until things settle down before upgrading.

Posted

Yea, I reverted back, and still have my ticket open. They are saying because I am self-hosted that they can't touch it. :/  @csm, Should I just open a separate ticket that asks to just upgrade?

Posted

Yea, I reverted back, and still have my ticket open. They are saying because I am self-hosted that they can't touch it. :/  @csm, Should I just open a separate ticket that asks to just upgrade?

​As long as your site is working fine with no issues in 3.4 I would submit a ticket to have them up grade your site. If 3.4 has no issues I can't see why you're not covered but then again, what do I know :) If your sites running normal now and a issue comes up, then more than likely it's a bug and they will find it during upgrade.

Not sure what happened in your ticket, but I would think IPB would of mentioned what needed to be corrected at server level (You would need to make those corrections however) so you could run the software you purchased from them.

Posted

Windows as a server flat requires a knowledgeable windows system administrator. Just because it is easy to install does not at all mean any of the default configurations are suitable for usage, in fact quite the reverse.

​before I continue to get bashed for having windows, and not having a "knowledgeable windows sysadmin". I would like to point out a buddy of mine has a linux web server same tweaks (mem, and other plugins), and it does the same thing. Same database (copy), different OS. and point out that yes, I do know how to setup a server. The title flows into the message body.

Posted

 The title flows into the message body.

​I understood that...

I would like to point out a buddy of mine has a linux web server same tweaks (mem, and other plugins), and it does the same thing. 

You compare apples and oranges. Regardless, configuring your own server and using windows means any and all server issues land at your feet, and the number of people knowledgeable enough to assist is far lower. Not an ideal situation nor one I would be willing to put up with, managed hosting services exist for a reason.

Posted

​I understood that...

You compare apples and oranges. Regardless, configuring your own server and using windows means any and all server issues land at your feet, and the number of people knowledgeable enough to assist is far lower. Not an ideal situation nor one I would be willing to put up with, managed hosting services exist for a reason.

​There is a reason why different flavours of servers exist. Windows and dedicated (unmanaged), is the cheap option at this time. I do not have the money to dump constantly. So immediately bashing windows, and continuing to contribute nothing, seems to be more trollish behaviour than anything. If you cannot contribute assistance or insight without being a troll, then don't reply. Simple as that.

Posted

I have used Windows server 2012 with IIS to serve 3.4.x for 2 years, i moved a couple of months ago to CentOS+NGINX, so in fact i have used both. From my experience, every involved part has a share on what concerns to culpability.



Invision Power is guilty

  • From what i've seen, IPS hates Windows. I am pretty sure they've never tested their products on a windows environment. Whenever i submitted a ticket, as soon as i told i was running windows srv 2012, they just "pulled the plug" on the ticket. This happened several times. I stated this repeatedly and i'll continue to state it over and over: if IP doesn't support the installation of IPS on Windows, they should clearly state it to customers. I had lots of character encoding problems and no one at IP cared about that. There is no rationale in paying for a non-existent support. So from IP side, expect Linux to get all the love. If you are on windows, you are at your own. I had to debug by myself all the issues i've came across...
  • There is a .htaccess file provided by IP, but where is the Web.config for iis users? (i know, nginx would also need it, but just to reinforce my previous point..)
  • Windows implements an UTF-8 charset called Windows-1252 which corresponds to UTF8-MB4 (needs 4 bytes per character - the proper UTF8). Unfortunately, there was no support for UTF8-MB4 in IPB 3.4.x. I have not tested myself 4.0 to see if does now. So it is likely that you end up running into encoding issues that if you are not aware of them will spoil your database.


PHP is guilty

  • PHP implementation on windows sucks in some aspects, and has some inconsistencies, in what concerns to locales, character conversion from windows-obtained data (the € sign is badly converted, for example...)


Windows is Guilty

  • Windows is quite powerful, but i tend to agree with Marcher: it needs more knowledge than linux in what concerns to web serving. I am an IT Engineer (though my area of expertise is not Web serving or web programming, i understand the "basics" of it) and in one week i was able to set up a centOS+nginx web server while windows+iis took me months to understand and master.

 

Being so, i think you should check the integrity of your DB first, then start upgrading with https disabled. View the upgrade process as risky and take an incremental approach. As soon as you get your board running smoothly, you can try enabling HTTPS.

 

  • Management
Posted

I have used Windows server 2012 with IIS to serve 3.4.x for 2 years, i moved a couple of months ago to CentOS+NGINX, so in fact i have used both. From my experience, every involved part has a share on what concerns to culpability.



Invision Power is guilty

  • From what i've seen, IPS hates Windows. I am pretty sure they've never tested their products on a windows environment. Whenever i submitted a ticket, as soon as i told i was running windows srv 2012, they just "pulled the plug" on the ticket. This happened several times. I stated this repeatedly and i'll continue to state it over and over: if IP doesn't support the installation of IPS on Windows, they should clearly state it to customers. I had lots of character encoding problems and no one at IP cared about that. There is no rationale in paying for a non-existent support. So from IP side, expect Linux to get all the love. If you are on windows, you are at your own. I had to debug by myself all the issues i've came across...
  • There is a .htaccess file provided by IP, but where is the Web.config for iis users? (i know, nginx would also need it, but just to reinforce my previous point..)
  • Windows implements an UTF-8 charset called Windows-1252 which corresponds to UTF8-MB4 (needs 4 bytes per character - the proper UTF8). Unfortunately, there was no support for UTF8-MB4 in IPB 3.4.x. I have not tested myself 4.0 to see if does now. So it is likely that you end up running into encoding issues that if you are not aware of them will spoil your database.

Actually, roughly half of the development team develop on Windows. You are right though, we aren't fans of Windows/IIS environments, primarily because 1) Many, if not most, aren't setup properly.  2) As you've eluded to, PHP on Windows is, in may regards, an afterthought. I'd argue that it just doesn't belong. If you need a .NET environment, use what's appropriate - Windows. If you need a PHP and MySQL environment, use what's appropriate - Linux. Both serve their purposes well, but PHP on Windows is a constant battle. Even Microsoft uses Linux. :)

To that end, you are correct that we should be more clear regarding our policy and requirements and we will certainly do that. We develop and support the software based on the masses... and the masses overwhelmingly use LAMP or LEMP. If you encounter an outright bug, by all means please use the bug tracker for further evaluation. We cannot, however, provide server advice or assistance with Windows environments... so few of our clients use such a configuration, our experience and expertise is limited. What experience and expertise we do have leads us to believe that Windows servers to serve PHP are more trouble than they're worth. 

 

Posted

I apologize, didn't realize you were on a windows server. That bug / or related to I believe has been fixed recently however, it may be a bit before that specific issue is released in a version.

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...