Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Bunstonious
76
Support / Re: error 500 after server change
« on March 23rd, 2014, 10:02 PM »Can you please put the last lines of your log here?
77
Support / Re: error 500 after server change
« on March 22nd, 2014, 12:42 PM »It only shows up if you MOVE the data from a server to another, not if you create the data on the final server..?
Then it's a permission issue, isn't it...??!
Short of a magic wand, not sure what other permission I can check :P
79
Support / Re: error 500 after server change
« on March 21st, 2014, 03:50 AM »I'm SOOOO behind when it comes to providing tech support (Bunstonious, txcas and Wanchoppe, I think they're all waiting for my feedback on something, it's just that I don't remember what.)
I have no idea what the problem could be with FCGI, but quite honestly, last time I tried Wedge on such a server, it frigging worked....... :-/
* Nao hates lousy servers with weird settings.
Seriously though, it's because I am in Aus... And I host myself (because I am le poor).
This particular issue happened when I went from my hosted server to my VPS, and I can confirm that I can install a fresh copy of wedge to my VPS so it meets the requirements, so I am unsure why it is giving the 500 error.
80
Support / Re: error 500 after server change
« on March 20th, 2014, 12:57 AM »
That's interesting.
I checked mine and it is using Apache Mod, not FastCGI.
I checked mine and it is using Apache Mod, not FastCGI.
81
Support / Re: error 500 after server change
« on March 19th, 2014, 12:35 PM »
Starting to think it's a cache or plugin issue.
I used my test install and changed the database to my main forum and the main page loaded ok (pretty URL's broken).
What settings control the cache (eg, can you remove it and get it to rebuild)?
I used my test install and changed the database to my main forum and the main page loaded ok (pretty URL's broken).
What settings control the cache (eg, can you remove it and get it to rebuild)?
82
Support / Re: error 500 after server change
« on March 19th, 2014, 07:55 AM »
Update: I was able to install a stock current version of Wedge, still get the internal server error with my main forum (I copied current files from GitHub).
Is there any way with the URL to "run it in safe mode"?
Is there any way with the URL to "run it in safe mode"?
83
Support / Re: error 500 after server change
« on March 19th, 2014, 04:56 AM »
I am getting this same error message when I moved from an internally hosted server to a VPS.
I can confirm it is not a permissions issue (checked that) but I will do some testing on the train home.
The test I will perform is trying to install a test wedge site and see if I am missing any of the requirements.
I can confirm it is not a permissions issue (checked that) but I will do some testing on the train home.
The test I will perform is trying to install a test wedge site and see if I am missing any of the requirements.
84
Features / Re: +1 > Like
« on March 12th, 2014, 04:02 AM »
When I get my website back (moved house and have no internets) I will work on changing to a +1 button (maybe even a graphic).
86
Features / Re: Poll: dropping oldIE
« on March 12th, 2014, 03:56 AM »There's always a flag to restore old OSes... Just add 'allow_jurassic_crap' to the settings table, and set it to 1.
I could also (1) make it not hidden, and (2) make it enabled by default, but I don't know to which extent people are interested in keeping support for OSes that haven't been patched for security in at least 8 years (for Windows 2000), more for the others...
- Not to be cumbersome to other browsers. That is, if a hack forces me to make a chance for other browsers, or if it adds bytes for all browsers (which it never will, thanks to Wess!), then it's a no-go for me.
Basically, I use Classic Shell, it does 95% of the job. :P
87
Features / Re: Poll: dropping oldIE
« on March 10th, 2014, 09:20 AM »You're mixing things up.Quote from Bunstonious on March 9th, 2014, 11:33 PM I don't think it should be blocked, just include a banner saying its unsupported, then remove the hacks to make it work.
IE 6-IE 7 = unsupported. They currently look bad. But any good looking modern website will break horribly on them.
Old Windows = blocked. Not blocked "because they're unsupported"... Blocked because approximately 0.01% web visitors are actually using one of these, and a MUCH higher number of web visitors using this are actually spam bots.
I guess it comes to a point where you decide what you want the project to be (and draw a line in the sand).
Cutting Edge and Nimble or Encumbered by hacks for old browsers.
Up to you I guess, you are the project steward (although the poll seems in favour of dropping support for OldIE).
I personally stayed with Win XP until my PC broke down a couple of years ago and I was forced to reinstall everything anyway.
I tend to tweak my OSes a lot, so I like keeping them that way. I have the same problem with my Galaxy S3 right now, ahah, can't upgrade to KitKat...
Anyway. WordPress blogs using BB will actually block any requests coming from Windows 2000 and below. What else?
88
Features / Re: Poll: dropping oldIE
« on March 9th, 2014, 11:33 PM »
I don't think it should be blocked, just include a banner saying its unsupported, then remove the hacks to make it work.
If they want to use an old browser, more sites than wedge.Org are going to not work.
PS: I use a mix of Chrome / IE. Tablet is 11 I think, and work is 9 or 10
If they want to use an old browser, more sites than wedge.Org are going to not work.
PS: I use a mix of Chrome / IE. Tablet is 11 I think, and work is 9 or 10
89
Features / Re: Poll: dropping oldIE
« on March 5th, 2014, 12:09 PM »
I think all that should be supported are browsers that m$ provide security updates.
Once they drop doing security updates, drop support.
We as experienced IT guys need to be proponents of software updates, because if we don't then no one will.
I can only see this as an issue for organisations, however they also need to be more forthcoming with software updates and if they MUST use an older browser, Citrix it.
Once they drop doing security updates, drop support.
We as experienced IT guys need to be proponents of software updates, because if we don't then no one will.
I can only see this as an issue for organisations, however they also need to be more forthcoming with software updates and if they MUST use an older browser, Citrix it.
90
Off-topic / Re: Twitter
« on March 4th, 2014, 01:05 AM »
I'd day not, Facebook isn't even updated.
For updates come to wedge.org I guess
For updates come to wedge.org I guess