Wedge repo -- installation feedback

Norodo

  • Oh you Baidu, so randumb. (60 sites being indexed at once? Jeez)
  • Posts: 469
Re: Wedge repo -- installation feedback
« Reply #75, on January 26th, 2014, 03:00 PM »
Right so the first topic I created apparently DID get posted, but entering it is another story:

Code: [Select]
Warning: min(): Array must contain at least one element in /Users/Finn/Sites/wedge/gz/app/Display.php on line 794

Warning: max(): Array must contain at least one element in /Users/Finn/Sites/wedge/gz/app/Display.php on line 826

Code: [Select]
Wrong value type sent to the database. Integer expected. (id_msg)

Code: [Select]
Notice: Undefined index: nav_buttons in /Users/Finn/Sites/wedge/core/html/Display.template.php on line 374

Warning: Invalid argument supplied for foreach() in /Users/Finn/Sites/wedge/core/html/index.template.php on line 815
Pages: 1  Go Down

Notice: Undefined index: get_message in /Users/Finn/Sites/wedge/core/html/Display.template.php on line 40

Fatal error: Function name must be a string in /Users/Finn/Sites/wedge/core/html/Display.template.php on line 40

Nao

  • Dadman with a boy
  • Posts: 16,063
Re: Wedge repo -- installation feedback
« Reply #76, on January 26th, 2014, 10:44 PM »
@Powerbob, mass upload is now fixed. :)

@Norodo, okay I'm getting lost... Is your install the broken one? The one with the errors 500? Do I still need to log into your site and look into that one? As for the errors here: I'm really, REALLY not getting them on a freshly installed Wedge forum... And the id_msg error, does your error log say where it's located?

MultiformeIngegno

  • Posts: 1,337
Re: Wedge repo -- installation feedback
« Reply #77, on January 26th, 2014, 11:01 PM »
I just downloaded the zip from GitHub, uploaded to my VPS (PHP 5.5.8, nginx 1.5.9), chmodded all the files to 775 and chowned to www-data (which is in the root group). Stylings have something wrong..: http://ffio.it/install.php
Posted: January 26th, 2014, 10:58 PM

I get a 404 when I try to load the CSS file
Posted: January 26th, 2014, 11:00 PM

Ok now it works! It was CloudFlare's fault... -_-

Norodo

  • Oh you Baidu, so randumb. (60 sites being indexed at once? Jeez)
  • Posts: 469
Re: Wedge repo -- installation feedback
« Reply #78, on January 27th, 2014, 01:13 AM »Last edited on January 27th, 2014, 01:32 AM
Quote from Nao on January 26th, 2014, 10:44 PM
@Norodo, okay I'm getting lost... Is your install the broken one? The one with the errors 500? Do I still need to log into your site and look into that one? As for the errors here: I'm really, REALLY not getting them on a freshly installed Wedge forum... And the id_msg error, does your error log say where it's located?
My install is still broken. As I said I made a localhost install to see if it would work there, and it kind of did. I'd still prefer if it worked on my remote though. It's probably outdated by now.

But yes, if you would log in and have a look that'd probably be a good idea.

I just noticed someone talking about cloudflare. Maybe my issue lies there. brb testing.

Harz-FEAR

  • Posts: 12
Re: Wedge repo -- installation feedback
« Reply #80, on January 27th, 2014, 02:45 AM »
The google CDN for jquery isn't loading, and it's somehow ironic that you can't change the jquery CDN if the CDN isn't reachable.

MultiformeIngegno

  • Posts: 1,337
Re: Wedge repo -- installation feedback
« Reply #81, on January 27th, 2014, 09:58 AM »
Quote from Harz-FEAR on January 27th, 2014, 02:45 AM
The google CDN for jquery isn't loading, and it's somehow ironic that you can't change the jquery CDN if the CDN isn't reachable.
Actually you can change CDN. You mean to change it automatically when it's down?

Nao

  • Dadman with a boy
  • Posts: 16,063
Re: Wedge repo -- installation feedback
« Reply #82, on January 27th, 2014, 10:14 AM »
I know that soft-merging is cool, but if you're adding to your earlier post (e.g. they're thematically linked), please click the Merge button afterwards to hard-merge them together, because otherwise what I get when I read posts (and I read them all from the Recent Posts section), is your last post, then your middle one, then your first one. Which can get confusing. Soft-merging is only for posts that you feel don't belong together, and can thus serve as new 'starting nodes' for threaded replies if this is ever implemented.
Quote from MultiformeIngegno on January 26th, 2014, 11:01 PM
I get a 404 when I try to load the CSS file
Would have helped to post the URL...
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. :^^;:
Re: Wedge repo -- installation feedback
« Reply #83, on January 27th, 2014, 10:20 AM »
Quote from MultiformeIngegno on January 27th, 2014, 09:58 AM
Quote from Harz-FEAR on January 27th, 2014, 02:45 AM
The google CDN for jquery isn't loading, and it's somehow ironic that you can't change the jquery CDN if the CDN isn't reachable.
Actually you can change CDN. You mean to change it automatically when it's down?
It's a problem I've been aware of for years, but Google never let me down for more than a few seconds, and I didn't expect they'd take so long to update their links. (See New Revs for a fix.)

The only 'sure-fire' solution is the widely documented <script> hack right after the CDN link. For instance, ElkArte implemented it (look at their source code, more particularly window.jQuery || document.write...)
The problem is, this adds over a hundred bytes to all pages. It's acceptable, but not something I'm looking forward to doing, especially given that Google never let me down until now. So, to me, it's been a bit of a waste of space...
Additionally, Wedge can't link directly to the jQuery files, because they're protected by htaccess. I used to do that to prevent people from looking into my JS code while the Wedge source code was heavily guarded, but it's no longer a problem. However, I could imagine that some people might want to write some extra scripts and hide them from view, and thus might enjoy this htaccess file too. (If they're writing a plugin, they can always take that file and put them into their own plugin folder, it should work the same.)
So, that would force me to do a 'dummy' gz version of the jQuery files, which is fine by me, but not yet implemented, ah ah. (Because JS files are only gzipped as they're requested, and when using a CDN, the local jQuery is obviously never requested.)

Harz-FEAR

  • Posts: 12
Re: Wedge repo -- installation feedback
« Reply #84, on January 27th, 2014, 01:40 PM »
Quote from MultiformeIngegno on January 27th, 2014, 09:58 AM
Quote from Harz-FEAR on January 27th, 2014, 02:45 AM
The google CDN for jquery isn't loading, and it's somehow ironic that you can't change the jquery CDN if the CDN isn't reachable.
Actually you can change CDN. You mean to change it automatically when it's down?
No, you can't, the Selectbox doesn't appear when JQuery is missing, I had to go to the database and change it there.
Posted: January 27th, 2014, 01:35 PM
Quote from Nao on January 27th, 2014, 10:20 AM
The only 'sure-fire' solution is the widely documented <script> hack right after the CDN link.
Another solution would be to make the CDN selectbox not dependent on JQuery.

MultiformeIngegno

  • Posts: 1,337
Re: Wedge repo -- installation feedback
« Reply #85, on January 27th, 2014, 03:18 PM »
Quote from Harz-FEAR on January 27th, 2014, 01:40 PM
Quote from MultiformeIngegno on January 27th, 2014, 09:58 AM
Quote from Harz-FEAR on January 27th, 2014, 02:45 AM
The google CDN for jquery isn't loading, and it's somehow ironic that you can't change the jquery CDN if the CDN isn't reachable.
Actually you can change CDN. You mean to change it automatically when it's down?
No, you can't, the Selectbox doesn't appear when JQuery is missing, I had to go to the database and change it there.
I used firebug :P

Nao

  • Dadman with a boy
  • Posts: 16,063
Re: Wedge repo -- installation feedback
« Reply #86, on January 27th, 2014, 04:26 PM »
Quote from Harz-FEAR on January 27th, 2014, 01:40 PM
No, you can't, the Selectbox doesn't appear when JQuery is missing, I had to go to the database and change it there.
Like Lorenzo explained, you can force 'visibility' to visible in dev tools, and then get your value changed.
Quote from Harz-FEAR on January 27th, 2014, 01:40 PM
Another solution would be to make the CDN selectbox not dependent on JQuery.
Nope... The script relies way too much on jQuery to work its magic. It would be at least double the size otherwise.
I'd rather not set visibility:hidden instead of that. And that would mean a FOUC -- which to mean is heresy!

I'm still trying to evaluate the best way to do it.

In the meantime, I'm nearing completion of my installer rewrite. It doesn't change anything to you technically, but internally, it's pretty nice:
- it now creates all of your empty folders for you, meaning: (1) folder permissions will no longer be an issue, and (2) Wedge will now ship with only three folders: /assets (which you can usually skip after you install it once), /install (which you SHOULD skip after you install it once), and /core (which will have most of the changes between versions.)
- it installs directly from within install/, meaning you just need to upload all of the files to the server, point your browser to index.php, and you don't have to do anything else. Advantages: (1) noobs have one less daunting task to do, (2) I can actually release the software through GitHub, saving me a lot of time. :)

MultiformeIngegno

  • Posts: 1,337
Re: Wedge repo -- installation feedback
« Reply #87, on January 27th, 2014, 04:42 PM »
+1 for releasing through GitHub. At least it would mean not to risk the problems SMF had with 2.0.7 release (they had some issues with packages, they updated them at least 2 times after release without saying when and what changed).. With github there are commits. :)

Nao

  • Dadman with a boy
  • Posts: 16,063
Re: Wedge repo -- installation feedback
« Reply #88, on January 27th, 2014, 04:46 PM »
Yep... That's not specific to github, but I see what you mean. ;)

I have this feeling that Wedge is best distributed over at github.com, because it's easy to download everything you need from a familiar interface. I'll try to build a 'download page' on wedge.org, but it'll be only a list of links to the actual github pages.

So, there's a SMF 2.0.7 out and no one told me..? Security fixes? Am I not supposed to integrate it into Wedge then..?! (I don't care about SMF 2.1, but Wedge is based on the 2.0 line, so it needs these.)