« Git problems
Wedge repo -- installation feedback
Translating Wedge to Spanish - Need a little help »

Farjo

  • "a valuable asset to the community"
  • Posts: 492
Re: Wedge repo -- installation feedback
« Reply #150, on February 3rd, 2014, 02:16 AM »
This is what's set up on mine:

Subdomains.Root Domain = wedge.domain.tld

Document Root = /wedge

Redirection = Not redirected

NB index.php is not used nor is the trailing slash. What are your settings?

Obake

  • You humans are ruining your planet.
  • Posts: 17
Re: Wedge repo -- installation feedback
« Reply #151, on February 3rd, 2014, 03:55 AM »
I think I may need to practice some patients here concerning this sub-domain. Essentially my settings are the same as yours but for my domain. No redirect, built as Type A in Zone, domain is wedge.domain.net, document root is public_html/wedge.

All good as far as I can see but I think I am being caught between sub-domain propgation and the server move. The propgation seems to be quick, about 4 or so hours but later this evening I found the sub-domain had been changed back to the old sub. I think this occurred after the server updated and pushed out the move but some how kept the old sub-domain name. I had previously changed the sub name for simplicty and then later deleted the sub-domain before the server move. That was likely a judgement error on my part. To make it worse, the domains were on one server and the host another. Quite frankly I screwed myself on this one by being impatient and thinking all the propagation had taken place. :)  Anyway, the domains have been moved to the host and I will wait a day or two to give all this time to propgate.

Thanks.  :)
Re: Wedge repo -- installation feedback
« Reply #152, on February 3rd, 2014, 05:20 AM »
All is good. Wedge is now installed as a sub-domain. Went without a hitch.  :)

Patience is a virtue I am told.  :)

Nao

  • Dadman with a boy
  • Posts: 16,080
Re: Wedge repo -- installation feedback
« Reply #153, on February 3rd, 2014, 04:15 PM »
@Maxx, Weaving is supposed to be the 'dry' skin, for those who like their CSS to be simple.
However, I still find it too verbose. I'm looking for someone to help me remove a few kilobytes of styles, and move them to Wilde and things like that. The problem is here: it needs to still *look good* after de-styling it. I only managed to remove a few hundred bytes by optimizing unordered lists, and even that, I haven't yet finished doing. (No commit.)
A nightmare... Well, for the perfectionist that I am, I guess.

@Obake, if it's only about the color set, why not 'fork' Wilde and apply its colors to it..? I'd be interested in seeing the results. :P

The 'bug' in OriginalFiles.php is (still) due to your script running PHP 5.2, not PHP 5.3. Sorry about that, but...

Not only does Wedge support subdomains, but unlike SMF, it supports *per-board* subdomains, just like Noisen.com does. I'm not using these here because I've been planning (for so many years ahah) to use a cookie-less sub-domain for asset retrievals, at least to test performance between with/without.

I'd recommend you enable a wildcard for subdomains, if your host allows it!
Re: Wedge repo -- installation feedback
« Reply #154, on February 3rd, 2014, 08:46 PM »
Quote
@Maxx, Weaving is supposed to be the 'dry' skin, for those who like their CSS to be simple.
However, I still find it too verbose. I'm looking for someone to help me remove a few kilobytes of styles, and move them to Wilde and things like that. The problem is here: it needs to still *look good* after de-styling it. I only managed to remove a few hundred bytes by optimizing unordered lists, and even that, I haven't yet finished doing. (No commit.)
A nightmare... Well, for the perfectionist that I am, I guess.
Gonna PM you!

regards,
Maxx

Wanchope

  • Posts: 234
Re: Wedge repo -- installation feedback
« Reply #155, on March 12th, 2014, 11:53 AM »
I downloaded the wedge master zip file from the repo - using the wget command, unzipped and pointed my browser to the wedge directory
Code: [Select]
54.186.53.116/wedge/

it is showing blank page.

Farjo

  • "a valuable asset to the community"
  • Posts: 492

Wanchope

  • Posts: 234

Nao

  • Dadman with a boy
  • Posts: 16,080

Wanchope

  • Posts: 234

Nao

  • Dadman with a boy
  • Posts: 16,080
Re: Wedge repo -- installation feedback
« Reply #161, on March 12th, 2014, 07:57 PM »
That's because you server marks gz files with the wrong mime type. Did it create the gz/css/.htaccess file or not?

kimikelku

  • Posts: 61

Wanchope

  • Posts: 234
Re: Wedge repo -- installation feedback
« Reply #163, on March 13th, 2014, 03:14 AM »
Yes they were all created but I thing the problem might be from the wrong .htaccess configuration but I deleted all the content of the .htaccess files and created a copied the the working one from another installation which was working but yet it cant work. Here is the content of the  .htaccess file in use

Code: [Select]
#
# This is the .htaccess file. It redirects Apache requests to the proper place.
# If you're not using Apache, you'll need to adapt it to your HTTP server.
#
# @package Wedge
# @copyright 2010 René-Gilles Deberdt, wedge.org
# @license http://wedge.org/license/
# @author see contributors.txt
#

# Don't allow access to the Settings.php no matter what.
<FilesMatch "^Settings(_bak)?\.php$">
Order Deny,Allow
Deny from all
Allow from localhost
</FilesMatch>

<IfModule mod_headers.c>
# Unencrypted avatars should be cached for a very long time.
<FilesMatch "avatar_[0-9]_[0-9]+\.(jpg|jpeg|png|gif)$">
Header set Expires "Thu, 21 March 2025 03:42:00 GMT"
</FilesMatch>
</IfModule>

# Setting PHP variables is only supported in mod_php. If using PHP as CGI, edit php.ini instead.
<IfModule mod_php.c>

# Apache 2 uses php_value
<IfDefine APACHE2>
# PHP has to be running for Wedge to work, of course.
php_value engine 1

############### Security ###############
# Using cookies for sessions is much more secure.
php_value session.use_cookies 1
# If it is really necessary, Wedge will do this - and it does it better.
php_value session.use_trans_sid 0
# This is generally a bad thing to have on unless you need it on.
php_value register_globals 0
# This setting goes against Wedge's expectations on secure request variables.
php_value magic_quotes_sybase 0

############ Functionality #############
# If the session is automatically started, output compression may not work.
php_value session.auto_start 0
# A longer session length is preferrable when posting long messages.
php_value session.gc_maxlifetime 2880
# Wedge expects these options to be set normally. (They almost always are.)
php_value session.save_handler "files"
php_value session.serialize_handler "php"
# URL-based sessions are used if cookies aren't available to the client.
php_value session.use_only_cookies 0
# With this on, you can use the plugin manager among other things.
php_value allow_url_fopen 1
# This is here just for validation, although it isn't really used.
php_value arg_separator.output "&"
# This sets a larger upload file size.
php_value upload_max_filesize "4M"

############# Optimization #############
# If PHP does this, Wedge won't have to redo it.
php_value arg_separator.input "&;"
# There's no need to do these two, since Wedge doesn't use them.
php_value always_populate_raw_post_data 0
php_value register_argc_argv 0
# Magic quotes suck. Die. Forever.
php_value magic_quotes_gpc 0
# This is a really bad setting for connections, and is best off just generally.
php_value implicit_flush 0
</IfDefine>

# Apache 1 uses php_flag
<IfDefine !APACHE2>
php_flag engine on

############### Security ###############
php_flag session.use_cookies on
php_flag session.use_trans_sid off
php_flag register_globals off
php_flag magic_quotes_sybase off

############ Functionality #############
php_flag session.auto_start off
php_value session.gc_maxlifetime 2880
php_value session.save_handler "files"
php_value session.serialize_handler "php"
php_flag session.use_only_cookies off
php_flag allow_url_fopen on
php_value arg_separator.output "&"
php_value upload_max_filesize "4M"

############# Optimization #############
php_value arg_separator.input "&;"
php_flag always_populate_raw_post_data off
php_flag register_argc_argv off
php_flag magic_quotes_gpc off
php_flag implicit_flush off
</IfDefine>
</IfModule>

# Ensures that accessing your forum root with "/" instead of "/index.php" will work.
# Superceded by the Pretty URLs rule below, anyway.
<IfModule mod_dir.c>
DirectoryIndex index.php
</IfModule>

# Pretty URLs
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule .* index.php [L]
</IfModule>

Nao

  • Dadman with a boy
  • Posts: 16,080
Re: Wedge repo -- installation feedback
« Reply #164, on March 13th, 2014, 07:16 AM »
I'll need ftp access to your server for further support.

Kimi, that solution is a copout to me. CSS and js gzipping has always worked perfectly on all apache servers I tested. And Wedge doesn't enable it on non-apache servers by default.
« Git problems
Translating Wedge to Spanish - Need a little help »