This topic was marked solved by Nao, on June 6th, 2013, 12:05 PM

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
When we unite against a common enemy that attacks our ethos, it nurtures group solidarity. Trolls are sensational, yes, but we keep everyone honest. | Game Memorial

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Updated CSS code is buggy
« Reply #16, on June 3rd, 2013, 07:37 AM »
So, did they actually remove it, or not..?

And if it's free, it can be reopened again, right..?
Can you at least share the URL? :^^;:

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Updated CSS code is buggy
« Reply #17, on June 3rd, 2013, 04:07 PM »
They haven't removed it yet. I see why they think I don't have a site, I put everything in /forum/ rather than public_html but that was for a reason.

I can see why users have trouble with FTP details... the FTP details have no correlation to the account that I use to sign in...

Nao

  • Dadman with a boy
  • Posts: 16,082

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Updated CSS code is buggy
« Reply #19, on June 3rd, 2013, 08:26 PM »
But I provided you with the actual FTP details which should work (they work for me in FileZilla)

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Updated CSS code is buggy
« Reply #20, on June 4th, 2013, 05:10 PM »
Oh, sorry, I'd simply missed your PM.

Phew...

Took me a friggin' HOUR to figure out what was happening.
Turns out, Wedge won't install on this, because they're just incompetent.

From their phpinfo:

pcre

PCRE (Perl Compatible Regular Expressions) Support   enabled
PCRE Library Version   6.6 06-Feb-2006


Yeah, not updated in 7 years...!!!!
And because of that, it doesn't support \h, which was added in v7.2, i.e. a year later.
And Wedge relies on \h for many things.

It's obviously something that can be fixed by changing \h to [\t ], but I don't know if it's worth it...

PS: I didn't bother to do the conversion and try to finish the install process... Really, really couldn't bother. Do it if you're curious ;)

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Updated CSS code is buggy
« Reply #22, on June 5th, 2013, 11:25 AM »
I don't know, since indeed it's bundled by default... (5.2.4 + 7.2, how lucky!)

My guess, is that they always install PHP with PCRE disabled by default, and they somehow installed PCRE at some point, but long ago, and never cared to update it...

And yes, that totally sucks. But things like that, should be eye-openers for people who use crappy free hosting, I guess..!
There are enough decent free hosts, really, that we don't need to waste time on these ones, so I decided to just give up on this kind of host, it'll save us time in the long run.
Posted: June 5th, 2013, 11:24 AM

Oh, regarding the id_from_member/id_member_from bug... I know why I didn't find it immediately!
As the bug was in __create(), the first thing I did was look for all Notification object instances... But, this particular one was called with 'self'! So, bam... Never noticed it! I should have been more careful, when incorporating the original patch, I guess.

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Updated CSS code is buggy
« Reply #23, on June 5th, 2013, 02:14 PM »
I only found it because I forced every error to include a full backtrace.

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Updated CSS code is buggy
« Reply #24, on June 5th, 2013, 04:06 PM »
So you didn't notice the name inversion either..? ^^
Posted: June 5th, 2013, 04:05 PM

And how did you test, with two local accounts, maybe..?

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Updated CSS code is buggy
« Reply #25, on June 5th, 2013, 09:39 PM »
I didn't notice the inversion :/

I normally have half a dozen local accounts, until I wrote the merge-user code, now I only have two local accounts...