Wedge repo -- installation feedback

Nao

  • Dadman with a boy
  • Posts: 16,078
Re: Wedge repo -- installation feedback
« Reply #105, on January 27th, 2014, 11:41 PM »
Ouch...

Well, there's some Apache code in OriginalFiles, but it 'simply' ensures that htaccess files aren't copied if the server isn't Apache. So it should be working..?!

I guess I'll need access to your server at some point. (I'll have a bit more time to work on Wedge tomorrow, so I should be able to log into Norodo's test server and yours (if you want to share your credentials or create new ones of course))

Very sorry about the problem. I thought the whole new installer was pretty neat. Well, scratch that, I still think it's pretty neat. It just needs some more work to be perfect.

MultiformeIngegno

  • Posts: 1,337
Re: Wedge repo -- installation feedback
« Reply #106, on January 27th, 2014, 11:58 PM »
'kay, I'm deleting Wedge setup installed yesterday. I redownloaded the zip now, so I'll install it and then try the importer!

Nao

  • Dadman with a boy
  • Posts: 16,078
Re: Wedge repo -- installation feedback
« Reply #107, on January 28th, 2014, 12:08 AM »
Thanks, guys!
I know it's annoying to reinstall everytime (I really SHOULD add some feature to automatically delete existing tables if reinstalling over the same database), but I can't rely only on my experience to determine the installer is working 100%.

I'd really rather have fixed the 500 problem before going to sleep, but it'll all depend on whether Sven can fix the error on his side, or if he can give me access tomorrow.

MultiformeIngegno

  • Posts: 1,337
Re: Wedge repo -- installation feedback
« Reply #108, on January 28th, 2014, 12:09 AM »
Quote from Nao on January 27th, 2014, 10:14 AM
Quote from MultiformeIngegno on January 26th, 2014, 11:01 PM
Ok now it works! It was CloudFlare's fault... -_-
What with CloudFlare? Can you be specific..? I can't expect everyone on a CloudFlare-powered hosting to sort out their problems by themselves... Not everyone's as specialized in it as you are. :^^;:
Ehm, I don't know what CloudFlare's setting is in particular.. I just "paused" the domain in the CloudFlare panel and stylings started not giving me 404 error anymore.
I had problems with it (at some point.. before it was ok) with SMF too. It gave me (and gives me if I reactivate it now, I tested yesterday) a "session verification error" with CloudFlare on.
Re: Wedge repo -- installation feedback
« Reply #109, on January 28th, 2014, 12:09 AM »
Quote from Nao on January 28th, 2014, 12:08 AM
Thanks, guys!
I know it's annoying to reinstall everytime (I really SHOULD add some feature to automatically delete existing tables if reinstalling over the same database), but I can't rely only on my experience to determine the installer is working 100%.

I'd really rather have fixed the 500 problem before going to sleep, but it'll all depend on whether Sven can fix the error on his side, or if he can give me access tomorrow.
You can follow my setup progresses here: ffio.it :D
Re: Wedge repo -- installation feedback
« Reply #110, on January 28th, 2014, 12:12 AM »
Quote from MultiformeIngegno on January 28th, 2014, 12:09 AM
You can follow my setup progresses here: ffio.it :D
Mmmh.. really strange. I'm installing now in the same database I had the previous version (yesterday). Of course I'm setting now wedge2_ as prefix. But I get this:

Access denied for user 'root'@'localhost' (using password: NO)

Even if I entered another database username..

Pandos

  • Living on the edge of Wedge
  • Posts: 635
Re: Wedge repo -- installation feedback
« Reply #112, on January 28th, 2014, 12:15 AM »
Sorry Nao..
Was my fault.  Enabled server caching in cherokee. It's a no go :)
Installation went fine :) So you can have your peaceful sleep :)
# dpkg-reconfigure brain
error: brain is not installed or configured

Nao

  • Dadman with a boy
  • Posts: 16,078
Re: Wedge repo -- installation feedback
« Reply #113, on January 28th, 2014, 12:19 AM »
So what should I do with CF..?
Quote from MultiformeIngegno on January 28th, 2014, 12:12 AM
Mmmh.. really strange. I'm installing now in the same database I had the previous version (yesterday). Of course I'm setting now wedge2_ as prefix. But I get this:

Access denied for user 'root'@'localhost' (using password: NO)

Even if I entered another database username..
Hmm... I have no idea what it implies, sorry. :(
Is this a local Windows install..?

Okay, I'm really late now. See you tomorrow. Hope you can sort everything out and share!
Posted: January 28th, 2014, 12:17 AM

What's server caching, and what's Cherokee..? (Not a friend of Apaches, I guess. :P)

Maybe I should update the README saying that Cherokee and CloudFlare aren't supported..?

MultiformeIngegno

  • Posts: 1,337

Pandos

  • Living on the edge of Wedge
  • Posts: 635
Re: Wedge repo -- installation feedback
« Reply #116, on January 28th, 2014, 12:22 AM »
Cherokee is the fastest server around :)
Not only CF has problems. even Google PSS!
Wrote this month ago. There are several issues with Cloud services.

Nao

  • Dadman with a boy
  • Posts: 16,078
Re: Wedge repo -- installation feedback
« Reply #117, on January 28th, 2014, 12:23 AM »
Oh, the irony...

You must be using a very recent version of PHP. Recently they started deprecating mysql() functions.
It's an old importer script, and it was never converted to use mysqli(), unlike the rest of Wedge. Problem is the same on openimporter.
Either TE will fix it by tomorrow, or I'll look into it. In the meantime, you can always try to downgrade your PHP to 5.3, and retry importing.
Quote from Pandos on January 28th, 2014, 12:22 AM
Cherokee is the fastest server around :)
Not only CF has problems. even Google PSS!
Wrote this month ago. There are several issues with Cloud services.
Ahum... Well, dunno how to fix these, I'm afraid.

Pandos

  • Living on the edge of Wedge
  • Posts: 635
Re: Wedge repo -- installation feedback
« Reply #118, on January 28th, 2014, 12:24 AM »
Ups... forgot to answer:
Cherokee has very sophisticated content caching mechanisms, allowing it to cache anything (static files, dynamic content, etc.)