-
I was in the process of writing the blog post about it all. (Yesterday, I spent like an hour writing the README for the repo, so it felt comparatively faster.)
Anyway, yeah, the importer will be ready when it's ready, and since it still worked a few weeks ago, I'm guessing it doesn't require a lot of work, and I could even fix it now, but... Really, REALLY, all I want is to finish that pesky movie I was watching.
-
Hey
havoc Havok, you should have allowed @Nao to make the official announcement. He deserved it.
Posted: January 21st, 2014, 04:45 PM
Hey havoc Havok, you should have allowed @Nao to make the official announcement. He deserves it.
-
He just created a topic, but I made the announcement first (this post(http://wedge.org/pub/8338/repository-name-poll-yayer/msg292816/#msg292816)), and wrote a longer blog post to announce it 'properly'.
If we can't open ourselves to external scrutiny, then it should have remained a private project... ;)
-
Sorry to pour water on the start but I get this on step 6 and then the installer freezes :sob:
-
After unzipping Wedge and starting installation it notifies me that I do not have the languages folder:
(http://puu.sh/6sWKv.png)
Is this as intended?
-
You'll have to put install.php, install.sql, Settings.php and Settings.php.bak in your root folder.
-
That's what I get for not reading the instructions! I'll update my guide. :)
-
Sorry to pour water on the start but I get this on step 6 and then the installer freezes :sob:
-
We went through this before, I have the correct ones!
PHP 5.4.24
Mysql 5.5.34
-
I too get
Populated Database
Your settings have now been saved and the database has been populated with all the data required to get your forum up and running. Summary of population:
Created 86 tables.
Inserted 805 rows.
Some of the queries were not executed properly. This could be caused by an unsupported (development or old) version of your database software.
Technical information about the queries:
Line #640: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'unsigned NOT NULL default 1,
PRIMARY KEY (cat_order, id_cat),
UNIQUE id_cat ' at line 5
Line #647: Table 'wino_wedge.wedge_categories' doesn't exist
Line #691: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'unsigned NOT NULL default 0,
hidden tinyint(1) unsigned NOT NULL default 0,
' at line 6
Line #780: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'unsigned NOT NULL default 0,
PRIMARY KEY (id_lang, is_plugin, lang_file, lang_' at line 7
Line #1215: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'unsigned NOT NULL default 0,
PRIMARY KEY (id_mail),
KEY time_sent (time_sent' at line 10
Line #1254: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'unsigned NOT NULL default 0,
name varchar(255) NOT NULL default '',
descript' at line 4
Line #1289: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'unsigned NOT NULL default 0,
searchable bit(1) unsigned NOT NULL default 0,
' at line 6
Click "Continue" to progress to the admin account creation page.
EDIT:
BRB. Checking if this might be a side function of me forgetting to turn off safe-mode.
EDIT 2: Nope. Same problem persists on Apache 2.4, PHP 5.5 without safe_mode.
In addition I get this error when I open the root dir:
Warning: copy(/home/public/beta/wedge-master/gz/app/Class-System.php): failed to open stream: Permission denied in /home/public/beta/wedge-master/index.php on line 247
Warning: php_strip_whitespace(/home/public/beta/wedge-master/gz/app/Class-System.php): failed to open stream: No such file or directory in /home/public/beta/wedge-master/index.php on line 439
Warning: file_put_contents(/home/public/beta/wedge-master/gz/app/Class-System.php): failed to open stream: Permission denied in /home/public/beta/wedge-master/index.php on line 428
Warning: require_once(/home/public/beta/wedge-master/gz/app/Class-System.php): failed to open stream: No such file or directory in /home/public/beta/wedge-master/index.php on line 252
Fatal error: require_once(): Failed opening required '/home/public/beta/wedge-master/gz/app/Class-System.php' (include_path='.:/usr/local/php/5.5.8-nfsn1/lib/:/usr/local/php/lib/') in /home/public/beta/wedge-master/index.php on line 252
-
In the meantime, I have also noticed that the installer is unstyled.
Chrome console output:
Failed to load resource: the server responded with a status of 404 (Not Found) http://zeldaengine.net/beta/wedge-master/gz/css/install/chrome32-318221.css
Failed to load resource: the server responded with a status of 404 (Not Found) http://zeldaengine.net/beta/wedge-master/%3Cbr%20/%3E%3Cb%3EWarning%3C/b%3E…br%20/%3Ehttp://zeldaengine.net/beta/wedge-master/gz/js/script-m-318221.js
Uncaught TypeError: Object [object Object] has no method 'sb' install.php:101
event.returnValue is deprecated. Please use the standard event.preventDefault() instead.
-
Hmm... I guess it's because of the BIT(1) element.
Open install.sql, and replace all occurrences of bit(1) with tinyint(1) -- that should help.
I don't get why it doesn't work, though. The official MySQL website does say that it was introduced in v5.0.3, which is the minimum version Wedge will accept.
Perhaps an incompatibility in the install.php file, I don't know... Will look into it.
Great movie, BTW.
-
In addition I get this error when I open the root dir:
Warning: copy(/home/public/beta/wedge-master/gz/app/Class-System.php): failed to open stream: Permission denied in /home/public/beta/wedge-master/index.php on line 247
/gz/ and its sub-folders need to be writable (CHMOD 0755).
If /gz/ is writable, I *could* consider creating all of the sub-folders on the fly, either at install time or execution time. That would make less folders to fix, I don't know.
-
Hmm... I guess it's because of the BIT(1) element.
Open install.sql, and replace all occurrences of bit(1) with tinyint(1) -- that should help.
I don't get why it doesn't work, though. The official MySQL website does say that it was introduced in v5.0.3, which is the minimum version Wedge will accept.
Perhaps an incompatibility in the install.php file, I don't know... Will look into it.
Great movie, BTW.
Read somtimes about problems with unsigned BIT.
-
Hey havoc Havok, you should have allowed @Nao to make the official announcement. He deserves it.
:^^;:
-
Okay! I merged your post to the original topic (repo name poll), and split this topic from my first post, so it'll look more like a 'proper' topic. ;)
-
thank you, . i would not want to be at the receiving end of the wrath of pissed off coding geniuses.
-
Hmm... I guess it's because of the BIT(1) element.
Open install.sql, and replace all occurrences of bit(1) with tinyint(1) -- that should help.
I don't get why it doesn't work, though. The official MySQL website does say that it was introduced in v5.0.3, which is the minimum version Wedge will accept.
Perhaps an incompatibility in the install.php file, I don't know... Will look into it.
Great movie, BTW.
Installed perfectly :D :D :D
Click the link in my sig
-
You have to follow the instructions... :P
/gz/ and its sub-folders need to be writable (CHMOD 0755).
Either way, I changed /app/ to be writeable as well and now I get a 500 internal server error. Grand. :whistle:
I'll try to start from the top again...
-
Well, starting from the top again, chmod -Ring 777 to /gz/ and all the other folders specified at installation start, I got a little bit closer. Now I get an unstyled Wedge install.
Failed to load resource: the server responded with a status of 500 (Internal Server Error) http://zeldaengine.net/beta/wedge-master/gz/css/Wilde/chrome32-guest-326310.css.gz
Failed to load resource: the server responded with a status of 500 (Internal Server Error) http://zeldaengine.net/beta/wedge-master/gz/js/script-sha1-326310.js.gz
Uncaught ReferenceError: weUrl is not defined index.php?topic=1.msg1:218
Failed to load resource: the server responded with a status of 500 (Internal Server Error) http://zeldaengine.net/beta/wedge-master/gz/js/topic-326310.js.gz
Uncaught TypeError: Object [object Object] has no method 'mime' index.php?topic=1.msg1:222
(http://i.imgur.com/BnicBhPl.png)
-
Please try to login as admin and go to Server&Maintenace->General.
Disable "Enable compressed JS/css" and see if this do the trick for you.
-
CSS/JS is uncompressed when generated during the Wedge install process.... :-/
-
That does not seem to help, but it was a good idea. :)
Interesting. I'm going to poke around a bit.
-
Are you using Apache?
-
I'm trying to understand why compressing JS and CSS would generate a 500.
Okay, in Admin > Server > Settings (the first submenu), you should be able to choose what compression type to use. The default is Packer. Can you try other types, and tell me if they all generate a 500..? (Yes, included the uncompressed one.)
-
Perhaps my feedback is important, after the bit(1) change, deleting the DB tables and settings.php (recopy from master) I started install.php and it installed like dream.
Kudos Nao :cool: :cool: :cool:
Great work :D :D :D
-
I'm using Apache 2.4.
With Google Closure:
GET http://zeldaengine.net/beta/wedge-master/gz/css/Wilde/chrome32-admin-326310.css.gz 500 (Internal Server Error) index.php:13
GET http://zeldaengine.net/beta/wedge-master/gz/js/script-m-326310.js.gz 500 (Internal Server Error) index.php:21
With JsMin:
GET http://zeldaengine.net/beta/wedge-master/gz/js/script-m-326310.js.gz 500 (Internal Server Error) index.php:21
GET http://zeldaengine.net/beta/wedge-master/gz/css/Wilde/chrome32-admin-326310.css.gz 500 (Internal Server Error) index.php:13
With no minify:
GET http://zeldaengine.net/beta/wedge-master/gz/css/Wilde/chrome32-admin-326310.css.gz 500 (Internal Server Error) index.php:13
GET http://zeldaengine.net/beta/wedge-master/gz/js/script-m-326310.js.gz 500 (Internal Server Error)
-
I'm going to try a quick reinstall...
One thing that is annoying is that web owns all cached files so I have to take posession over them.
-
As an aside, it also does this on install.
Failed to load resource: the server responded with a status of 500 (Internal Server Error) http://zeldaengine.net/beta/wedge-master/gz/js/script-m-326310.js
Failed to load resource: the server responded with a status of 500 (Internal Server Error) http://zeldaengine.net/beta/wedge-master/gz/css/install/chrome32-326310.css
Uncaught TypeError: Object [object Object] has no method 'sb'
-
Sorry, was out IRL.
In the meantime, I remembered that the only 500 errors I got lately were due to misconfigured htaccess files.
Since your files ARE getting generated, the problems is certainly with your gz folder (or its subfolders), either their permissions, or the .htaccess files in them. Does your server allow for htaccess files at all..?
Might be worth a FAQ entry, I guess.
-
Hm. Yes, my server allows .htaccess files. It's a fairly standard shared hosting AMP install, apart from the MariaDB.
This is the .htaccess file in the css folder:
<Files *.php>
Deny from all
</Files>
<Files index.php>
Allow from all
</Files>
<IfModule mod_mime.c>
AddEncoding x-gzip .gz
AddEncoding x-gzip .cgz
AddEncoding x-gzip .jgz
<FilesMatch "\.(js\.gz|jgz)$">
ForceType text/javascript
</FilesMatch>
<FilesMatch "\.(css\.gz|cgz)$">
ForceType text/css
</FilesMatch>
</IfModule>
<IfModule mod_headers.c>
Header set Cache-Control "max-age=2592000"
Header set Expires "Thu, 21 March 2025 03:42:00 GMT"
Header set Vary "Accept-Encoding"
</IfModule>
FileETag none
This is my root .htaccess (i keep software in subdirectories of this folder):
Options -MultiViews +FollowSymlinks -Indexes
<IfModule mod_security.c>
# Turn off mod_security filtering.
SecFilterEngine Off
# The below probably isn't needed, but better safe than sorry.
SecFilterScanPOST Off
</IfModule>
DirectoryIndex index.php portal.php index.xhtml
ExpiresActive On
ExpiresByType image/gif A2592000
ExpiresByType image/png A2592000
ExpiresByType image/jpg A2592000
ExpiresByType image/x-icon A2592000
ExpiresByType application/pdf A2592000
ExpiresByType application/x-javascript A2592000
ExpiresByType text/plain A2592000
ExpiresByType text/css A604800
<IfModule mod_env.c>
SetEnv SEO_SUPPORT 1
</IfModule>
</IfModule>
AddType application/x-7z-compressed 7z
<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE application/javascript text/css text/html text/xml
</IfModule>
-
Try deleting all of wedge's htaccess files first. Can you then access the CSS.gz file directly?
If not, try deleting the root one. If it doesn't work it's probably a perm issue. If it works, reupload the htaccess and try to delete small sections of it until you find which one crashes it.
-
Installation went smooth - but i also had to disable that 'compress files' option for proper display.
I see the following error in my just installed forum:
Apply Filter: Only show the error messages of this member fred
Apply Filter: Only show the error messages of this IP address 192.168.0.2 Today at 08:46 PM
Apply Filter: Only show the errors of this type Type of error: General
Apply Filter: Only show the error messages of this URL http://192.168.0.200/wedge/index.php?action=admin;area=serversettings;sa=cache;e…
Apply Filter: Only show the errors with the same message 2: array_merge(): Argument #3 is not an array
Apply Filter: Only show the errors from this file File: /var/www/wedge/gz/app/ManageServer.php
Line: 1
Apply Filter: Only show the error messages of this member fred
Apply Filter: Only show the error messages of this IP address 192.168.0.2 Today at 08:46 PM
Apply Filter: Only show the errors of this type Type of error: General
Apply Filter: Only show the error messages of this URL http://192.168.0.200/wedge/index.php?action=admin;area=serversettings;sa=cache;e…
Apply Filter: Only show the errors with the same message 2: array_combine(): Both parameters should have at least 1 element
Apply Filter: Only show the errors from this file File: /var/www/wedge/gz/app/ManageServer.php
Line: 1
-
That's an interesting one.
However, I can't make anything of your error log until your enable debugging in the Admin > Server > Debugging menu. This will disable PHP minification, and thus give us proper lines for the errors.
I could probably find the array_combine error, but there are too many array_merge's in there.
Re: importer
It's up and running; as I told Pandos in private, I fixed the importer to work on the latest version.
Unfortunately, I'm a bit in a hurry IRL, and will have to postpone everything by a couple of hours.
I'll try to (1) fix a minor bug in the importer, and (2) actually upload it somewhere, before I go to bed.
-
On my localost I get this message:
Your settings have now been saved and the database has been populated with all the data required to get your forum up and running. Summary of population:
Created 92 tables.
Inserted 800 rows.
Some of the queries were not executed properly. This could be caused by an unsupported (development or old) version of your database software.
Technical information about the queries:
Line #626: Field 'offlimits_msg' doesn't have a default value
Line #1735: Field 'data' doesn't have a default value
Click "Continue" to progress to the admin account creation page.
I am using:
Software: MySQL
Software version: 5.5.23 - MySQL Community Server (GPL)
Protocol version: 10
User: root@localhost
Server charset: UTF-8 Unicode (utf8)
-
http://dev.mysql.com/doc/refman/5.5/en/blob.html
"BLOB and TEXT columns cannot have DEFAULT values."
offlimits_msg and data both are TEXT columns.
How come you're getting an error on this, then..? And just these two? There are plenty of TEXT fields... :-/
-
First of all, congrats on this release! It sure looks like the work of two PHP gurus, hope this goes on and on. It looks quite promising, can't compare it to 2.1 yet because I haven't even take a peek at it.
Second, I got the same error @Farjo did and I also get this in the error log:
URL http://localhost:85/wedge/index.php
8: Undefined offset: 0
C:/wamp/www/wedge/gz/app/Subs-BoardIndex.php
Line: 25
I also get random "Unable to load the "Settings.english" language file." when I use the Wine theme.
Other than that, I'm quite fonding what you two achieved. Well done and congratulations!
-
I tried it again on my localhost and go the same message. However it works on my web space.
So the files are good, it's just my local zend that's got the issue. I don't know what info. you'd need (or probably where to find it). It's the free version, I installed it in July 2013 and have never upgraded it as I cannot work out how. The only app is phpMyAdmin 3.
-
@Farjo, are you using Xamp, WampServer or something else?
First of all, congrats on this release!
It sure looks like the work of two PHP gurus, hope this goes on and on.
For me, personally:
- Class-Skeleton.php, because (1) it's my first attempt at doing pure OOP programming, (2) the skeleton system is VASTLY superior to SMF's layer system.
- Subs-Cache.php, which has so many cool features.
- Class-CSS.php, and its wonderfully obfuscated code. Even I have some trouble reviewing it, from time to time, ah ah.
- script.js, gives you an idea of the amount of work that went behind rewriting SMF JavaScript code. I didn't simply integrate jQuery deeply into it -- I used all of my JavaScript knowledge to make the script as smooth, fast and short as possible. It's optimized *to the byte*. sbox.js is also an interesting piece of JS, in that it is superior to all the competition (jQuery plugins for select box replacements), and does it in *half the size* of the closest 'optimized' competitor (about 2KB gzipped). Again, a lot of work went into this.
For Pete -- I have to say, I think he would like to show off his ban code. Or perhaps his plugin code. He put many months of work into both of these, and it was all very carefully planned ahead. I'm pretty sure he'll push the SMF team into allowing these bits to make their way into SMF 3.0. In a few years time, then...It looks quite promising, can't compare it to 2.1 yet because I haven't even take a peek at it.
Anyway...
Last year, Pete posted a quick list of features from Wedge that aren't in SMF. (Yes, because he loved SMF and wanted to rejoin them. I'm confused right now.)
http://wedge.org/pub/smf/8175/smf-with-a-different-name-huh/
Of course, many more features were added since then.
I'm pretty positive that despite having talented people in its team (shout out to Suki), SMF has no way to catch up with Wedge, because by the time it does, Wedge will still be more advanced, because I'll be busy catching up with myself.
I'd recommend you compare Wedge with Elk instead. Apart from the silly name, it's better than SMF in every respect.Second, I got the same error @Farjo did and I also get this in the error log:
URL http://localhost:85/wedge/index.php
8: Undefined offset: 0
C:/wamp/www/wedge/gz/app/Subs-BoardIndex.php
Line: 25
Okay, I'll just disable this feature in my next commit. During alpha testing, it's unwise to make debugging harder by default... :^^;:I also get random "Unable to load the "Settings.english" language file." when I use the Wine theme.
I should have specified: the Theme handling code is STILL in Wedge, but it will eventually go. It does NOT work, obviously, because themes themselves don't exist anymore. I just thought that you guys would rather have Wedge earlier, than wait for me to clean everything up and make it look like themes never were here to begin with.Other than that, I'm quite fonding what you two achieved. Well done and congratulations!
I'll make sure to pass it along to Pete. (Well, of course I won't, but I'm sure he's reading.)
-
@Farjo, are you using Xamp, WampServer or something else?
Does that answer the question? If not I can follow instructions to find out more. And is it important given that it works on my web space?
-
I don't know. I just want to avoid having to do any boring tech support in the future. This single-handedly killed my enthusiasm in working on Kyodai Mahjongg back in 2006, and there's no reason to think I've changed.
Technically, Wedge is only officially supported on Apache, so you should disable ZendServer if you can, and enable Apache instead.
-
Fair enough to all that; like I say I have it running on the web so I can use that :)
-
Well done. On my test VM, extracting the file, the permissions weren't set so I had to set everything to 644/777, afterwards I then experienced issues with the wedge installer being "unthemed" (like in Norodo's pic), managed to get that installed anyway. Then I browsed to my profile to fix the theme problem. Going to admin, I get many file writing related problem, this all points to /gz/keys/ directory, I then fixed that directory to be writable. I'll do further testing here and figure out the problem with installing on my VM. This uses
MySQL version 5.5.33, PHP version 5.5.7-1~dotdeb.1, Apache/2.2.22 (Debian)
Now for my test-remote server that is not hosted on my computer (Free hosting service.) Uploading to my webhost, installing, no problems, it installed flawlessly. No theme problems too. This hosts uses:
MySQL version 5.1.71, PHP version 5.4.17, Apache version 2.2.24, Linux 2.6.32-358.23.2.el6.bl1.1.1_1.x86_64
(x10hosting uses litespeed for webserver.)
-
Well. I downloaded the zip file and uploaded to my server. There was no install.php in the root. Found it in the install directory. Tried to install from /install/install.php. This caused errors about not finding certain directories. Copied all files from from /install to root /. Ran the install again and everything installed without error. Deleted install.php from root and deleted the /install directory.
So far Wedge is installed on one of my sub-domains, wedge.helmer.co. Looking forward to the next release.
Grumpy Old Man,
John
-
Well. I downloaded the zip file and uploaded to my server. There was no install.php in the root.
Found it in the install directory. Tried to install from /install/install.php. This caused errors about not finding certain directories. Copied all files from from /install to root /.
Why does nobody read readme files..?
It even shows up in second position in the paragraph list.
http://github.com/Wedge/wedge/
There it is. Second paragraph. Installation. Mentions every step to follow.
The alpha package will ship with all install/ files in the root by default, but for the pre-alpha, I'm expecting people to at least read the readme... :whistle:Ran the install again and everything installed without error. Deleted install.php from root and deleted the /install directory.
So far Wedge is installed on one of my sub-domains, wedge.helmer.co. Looking forward to the next release.
-
Well done. On my test VM, extracting the file, the permissions weren't set so I had to set everything to 644/777,
afterwards I then experienced issues with the wedge installer being "unthemed" (like in Norodo's pic), managed to get that installed anyway. Then I browsed to my profile to fix the theme problem. Going to admin, I get many file writing related problem, this all points to /gz/keys/ directory, I then fixed that directory to be writable.
Now for my test-remote server that is not hosted on my computer (Free hosting service.) Uploading to my webhost, installing, no problems, it installed flawlessly. No theme problems too. This hosts uses:
-
Hmm... I guess it's because of the BIT(1) element.
Open install.sql, and replace all occurrences of bit(1) with tinyint(1) -- that should help.
I don't get why it doesn't work, though. The official MySQL website does say that it was introduced in v5.0.3, which is the minimum version Wedge will accept.
Perhaps an incompatibility in the install.php file, I don't know... Will look into it.
Great movie, BTW.
Read somtimes about problems with unsigned BIT.
http://www.xaprb.com/blog/2006/04/11/bit-values-in-mysql/
-
I install it on localhost and all went fine ;)
-
Did a clean install of Wedge Alpha on my Xampp running MySQL 5.0 and PHP 5.5, worked fine. I don't think MySQL 5.5 would be related to these problems, so it must be some kind of OS setting out there.
Pandos, do you mean you think BIT should be avoided? From what I could see, there are no bugs in the current implementation (except of course for the initial scare over unsigned bits), and the worst it can do is truncate results to 0 and 1. All I can do right now is just stick to bits when I'm sure I'll only be using a boolean value, because I think it's slightly misleading and lazy programming to add a 'is_something' column, with values 0 and 1, and then decide that you want to add value 2 to represent something else, closely related but not directly. Sure.
-
PHP 5.4 & MySQL 5.5 works fine too.
Dunno if it's worth the hassle.
Just use BIT where it's useful. And that's what you've done.
The only thing is that BIT column doesn't play nice with indexes. But at this time no problem here.
We just must keep in mind that BIT columns never ever should be unsigned.
-
Installed to my shared hosting account @ Ipage.com with the following configuration
Platform Type: Debian
MySQL Version: 5.5.32
Perl Version: 5.8.8
PHP Version: 5.3.13
Installed smoothly and works like a charm.
Time to fire up my vps account :).
-
On localhost is running fine and still playing around. Later I will try it on LEMP stack on my VPS.
-
I unchosed 'allow members to chose their own theme' in Manage and Install under Themes and Layouts and it broke the css.
-
I also noticed this happens to logged in members, guest does not experience the css break.
:edit: Not really logged in members, only break when I logged in as the admin!
-
I have now removed the root .htaccess and... Still getting 500s for the CSS.
I also get 'weUrl' is undefined in my error log.
Uncaught ReferenceError: weUrl is not defined index.php?action=skin;u=1:245
-
weUrl is part of script.js, so if your .gz files all generate an error 500, it's no wonder JavaScript will never initialize.
I guess I'll need access to your FTP, so that I can see what's wrong with your server.
-
I'll get a testing setup done and give you the details over PM sometime after dinner today.
-
The part to the theme in the theme settings is wrong, it says website.com/Theme; this is not a correct part.
-
Ubuntu 12.04, PHP 5.3.10, MySQL 5.5.32, apart from the bit(1) problem in the database, its working fine.
-
The part to the theme in the theme settings is wrong, it says website.com/Theme; this is not a correct part.
The BIT thingy is fixed....
-
The part to the theme in the theme settings is wrong, it says website.com/Theme; this is not a correct part.
The BIT thingy is fixed....
Ubuntu 12.04, PHP 5.3.10, MySQL 5.5.32, apart from the bit(1) problem in the database, its working fine.
-
There it is. Second paragraph. Installation. Mentions every step to follow.
The alpha package will ship with all install/ files in the root by default, but for the pre-alpha, I'm expecting people to at least read the readme... :whistle:
Oh... So you're elk.helmer.co over at Elk's?
The same as above about elk is also true about wedge.helmer.co. Give one or both a spin
Nao,
Please change my login name to wedge.helmerl.co might as well keep things consistent!
Thanks,
John
-
my server was at first "actively denying any connection" the first 3 times. i just kept retrying and finally it installed.
i havent tried the importer yet, but so far i am loving the look of the admin area. the layout looks sleek and easy to navigate. :eheh:
-
Help
i tried to do a reinstall on a new database but i am getting error msg.
The installer has detected that you have wedge already installed.
Pls delete existinh database tables and replace settings.php
i have done this but errot still persisting
deleting the folder with go daddy admin panel was leaving some residual files. when i used 3rd party ftp to delete the folder worked like a charm. back up and running
:eheh:
-
I've managed to install Wedge somewhere, finally. It's on my laptop localhost. I did get this error message while installing:
Some of the queries were not executed properly. This could be caused by an unsupported (development or old) version of your database software.
Technical information about the queries:
Line #626: Field 'offlimits_msg' doesn't have a default value
Line #1735: Field 'data' doesn't have a default value
But it seems to work. I run MySQL version: 5.6.15
In my error log I got:
2: filemtime(): stat failed for /Users/Finn/Sites/wedge/gz/cache.lock
But all I had to do was touch cache.lock to create the file and now it doesn't give that error any more.
I also got this after opening logs:
8: Undefined offset: 0
File: /Users/Finn/Sites/wedge/gz/app/Subs-BoardIndex.php
Line: 472
All in all it seems to work!
-
I'll get a testing setup done and give you the details over PM sometime after dinner today.
-
The part to the theme in the theme settings is wrong, it says website.com/Theme; this is not a correct part.
I already said multiple times that this section is not finished yet. Basically, I'm going to remove everything pertaining to themes, but I need to determine what I'll re-use for skin handling, and what I'll completely delete.
So, anything you see in there is NOT a bug.
-
There it is. Second paragraph. Installation. Mentions every step to follow.
The alpha package will ship with all install/ files in the root by default, but for the pre-alpha, I'm expecting people to at least read the readme... :whistle:
In the future, instead of doing guess work-- just put your cursor where you want to reply, and hit Shift+Enter or Ctrl+Enter, as indicated below the post box. This will cleanly cut the post at that place, and allow you to reply without breaking nested quotes. It also works for other BBCode tags, BTW.Give the man a brass ring. Yes, I am elk.helmer.co over at Elkarte. elk.helmer.co is one of my sub-domains dedicated for testing the elk software. If you do not have access tthato your own site, go register and send me a PM I will give you super user permissions to test with.
Please change my login name to wedge.helmerl.co might as well keep things consistent!
I won't hold people by the hand. If you're not comfortable with an author who expects his users to google things and reading existing posts instead of asking their questions, then you should be using either SMF or ElkArte. (I'd say ElkArte only, but I don't know their position on that specific point. SMF has dozens of members in their team so I expect they can handle support better than one person who also happens to be the lead developer.)
-
I've managed to install Wedge somewhere, finally. It's on my laptop localhost. I did get this error message while installing:
Some of the queries were not executed properly. This could be caused by an unsupported (development or old) version of your database software.
Technical information about the queries:
Line #626: Field 'offlimits_msg' doesn't have a default value
Line #1735: Field 'data' doesn't have a default value
http://dev.mysql.com/doc/refman/5.6/en/data-type-defaults.html
This makes absolutely no sense at all...
Especially since lines 626 and 1735 are both about adding data to the table, so it implies that the table was properly created.
I've added a few bytes to inserting dummy empty values, but honestly, I'm not thrilled with that... Does that mean you'll get the same errors when creating new boards and posting messages..?In my error log I got:
2: filemtime(): stat failed for /Users/Finn/Sites/wedge/gz/cache.lock
But all I had to do was touch cache.lock to create the file and now it doesn't give that error any more.
I also got this after opening logs:
8: Undefined offset: 0
File: /Users/Finn/Sites/wedge/gz/app/Subs-BoardIndex.php
Line: 472
All in all it seems to work!
On what page are you getting these errors, exactly?
-
Thanks, I'll have a look ASAP. A bit overwhelmed after taking a break yesterday...
Do I still need to look into it..?
I'd really like the install process to be as smooth as possible. Oh, I don't remember though... Was it post-install? A problem with 500 errors, right..?
-
This makes absolutely no sense at all...
Especially since lines 626 and 1735 are both about adding data to the table, so it implies that the table was properly created.
I've added a few bytes to inserting dummy empty values, but honestly, I'm not thrilled with that... Does that mean you'll get the same errors when creating new boards and posting messages..?
Yeah, well, doesn't make sense either... Or maybe you didn't chmod your /gz/ folder properly...? (It needs to be chmodded, like all of its children -- at least until I get to rewrite the install process, as mentioned above.)
Any reasons why Wedge should fail to find any board category..?
On what page are you getting these errors, exactly?
Sorry, just got home from a party. I'll probably be more constructive tomorrow!
-
I have an error in Media! Mass upload does not work? Does not work on Wedge .org either :whistle:
See below please :hmm:
-
I've added a few bytes to inserting dummy empty values, but honestly, I'm not thrilled with that... Does that mean you'll get the same errors when creating new boards and posting messages..?
Database Error
File: /Users/Finn/Sites/wedge/gz/app/Subs-Post.php
Line: 1225
When posting messages. Creating boards is okay though.Any reasons why Wedge should fail to find any board category..?
On what page are you getting these errors, exactly?
-
I'll look into mass upload. But are you sure it's not related to posting too big a file..?
@Norod, that line is the one that inserts new topics (not posts). I tried creating a new topic on my local site, and saw nothing special happen. What's the exact database error..? (Make sure SQL queries are enabled in the server > debug settings. I think it's over there.)
-
Bump @Norodo.
-
Right so the first topic I created apparently DID get posted, but entering it is another story:
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
Wrong value type sent to the database. Integer expected. (id_msg)
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
-
@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?
-
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, 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?
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.
-
Still doesn't seem to work: http://wedgetesting.nfshost.com/wedge/index.php
You have the other details. :)
-
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.
-
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.
-
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.
I get a 404 when I try to load the CSS file
Ok now it works! It was CloudFlare's fault... -_-
-
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.
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.)
-
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.
Posted: January 27th, 2014, 01:35 PM
The only 'sure-fire' solution is the widely documented <script> hack right after the CDN link.
-
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.
-
No, you can't, the Selectbox doesn't appear when JQuery is missing, I had to go to the database and change it there.
Another solution would be to make the CDN selectbox not dependent on JQuery.
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. :)
-
+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. :)
-
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.)
-
http://www.simplemachines.org/community/index.php?topic=517205.msg3660496#msg3660496
-
You shouldn't laugh at them for that... Anyone can get into a mess like that, even us. Well, you can laugh at them, but don't express it online. :P
Still, I'd like to know what this large patch 'fixes'... Isn't there a changelog somewhere..?
-
http://download.simplemachines.org/index.php?thanks;filename=smf_2-0-7_changelog.txt
They just had to say "packages updated". I knew about the packages update by reading other topics.
-
Empty file for me.
Anyway... The new installer is up! It works for me, but I fear it's a major rewrite and it *absolutely* needs some skilled testers, otherwise I'll never get it to work... :P
-
Eheh they have some problems with releases :p
-
Working changelog:
http://www.simplemachines.org/community/index.php?topic=517205.msg3659937#msg3659937
I'll test soon the installer with my forum: rockciclopedia.com/forum/
-
+ The install script can no longer be run by someone else than the admin. (index.php, install.php)
On a new install it dies with : hacking attempt ;)
And for the better feel: it would be nice to have an index.php file redirecting to install.php in /install
-
Further more:
If I comment out the stopper, than the following error appears:
This installer was unable to find the installer's language file or files. They should be found under:
/install/core/languages
But these files are located in /core/languages :)
-
To test the new installer. Remove all folders except for assets and core. Upload /assets/icons/media. Upload /install. Remove Settings.php. run index.php (NOT install/install.php!) Done.
Posted: January 27th, 2014, 10:21 PM
Also, upload the /core/app/OriginalFiles.php file.
I'm sorry, I forgot to add it to the repo. I'd indeed add it to the index, but forgot to hit F5 to refresh my file list, and thus it wasn't added to the changeset.
This should now work for everyone...
-
Error 500 and white screen
-
Oh... :-/
So, err... Are you sure you cleaned up your folders before doing that?
Please reupload everything from scratch. Should work then.
(It was probably a bad idea of mine to commit this all two hours before going to bed... -_-)
-
Sure. From scratch. :)
Tested again and it's the same result...
-
When does it happen? Immediately..?
After the 500 error, does Settings.php show up in the root?
Do the media, attachments, gz and plugins folders show up in the root?
-
Yes
-
Just to be clear: I've done a reinstall from scratch as well, on my remote server (well, on a wedge.org subfolder with a silly long name), and it works perfectly.
Make sure OriginalFiles is uploaded.
And also -- I forgot -- you should move install/.htaccess to the root. Just in case. I don't think OriginalFiles deals with that file. Maybe it's the culprit..??
-
I'm not using Apache or lighty.
So .htaccess is not working for any other servers than the above :)
And yes. All files are in the right place.
-
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.
-
'kay, I'm deleting Wedge setup installed yesterday. I redownloaded the zip now, so I'll install it and then try the importer!
-
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.
-
Ok now it works! It was CloudFlare's fault... -_-
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.
-
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
Access denied for user 'root'@'localhost' (using password: NO)
Even if I entered another database username..
-
Uh..it's working now.. I just tried again. Same procedure
Now I'm uploading the importer
-
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 :)
-
So what should I do with CF..?
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..
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..?
-
So what should I do with CF..?
The importer gives me this
-
Is this a local Windows install..?
G night see you tomorrow! :)
-
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.
-
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.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.
-
Ups... forgot to answer:
Cherokee has very sophisticated content caching mechanisms, allowing it to cache anything (static files, dynamic content, etc.)
-
Not only CF has problems. even Google PSS!
Wrote this month ago. There are several issues with Cloud services.
Will take this to a new topic.
-
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.
-
To test the new installer. Remove all folders except for assets and core. Upload /assets/icons/media. Upload /install. Remove Settings.php. run index.php (NOT install/install.php!) Done.
Posted: January 27th, 2014, 10:21 PM
Also, upload the /core/app/OriginalFiles.php file.
I'm sorry, I forgot to add it to the repo. I'd indeed add it to the index, but forgot to hit F5 to refresh my file list, and thus it wasn't added to the changeset.
This should now work for everyone...
On a side note, mass upload is still not working in this install.
-
Can you be more specific when you say something doesn't work...? Because it works perfectly for me now...
It was only broken due to a last-minute change long ago where I removed a test for the upcook query string, and replaced it for an AJAX test... Which was wrong on two levels: (1) I did the reverse of the test I was thinking about, (2) Flash-based uploads never use Ajax, they just use a regular request, so I had to actually force Ajax status in QueryString.php, which was a waste of time, (3) it also disrupted the template flow, and made it impossible to issue a proper response. Not my most glorious change in the codebase, indeed, but if there's one thing I can be proud of, it's that I don't have any problems recognizing my errors. In this case, it was a human error, and I'm happy it got a human solution. :P
/methinks he just wrote a Like-magnet./melikes Like-magnets./melikes Likes.
Oooooh, new bug! Inline me's! Yay! :lol:
-
Nope sorry, I get this error;
-
Lol... It's a typical mass upload error that's been here since the SMF days. It's not related to Wedge at all.
Just search for Aeva Media error 2038 on Google. :P
Posted: January 28th, 2014, 01:34 PM
To be more specific, most of these 2038's can be fixed by adding a crossdomain.xml file to your forum's root, with this content:
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-access-from domain="*.myforum.com" />
<allow-access-from domain="myforum.com" />
</cross-domain-policy>
Replace myforum with your actual URL, of course.
It might be another problem, but it's always about domains and subdomains, to my knowledge.
Rewriting mass upload to use Ajax is one of my next projects. But not a very priority, I'm afraid.
-
Nope sorry no change :whistle:
-
Read more docs. There are multiple solutions.
I won't commit to a 'fix' because this feature is only temp.
-
Ok Nao, no problem I can wait :cool:
Tried to install the new files from the repo with the new install on a new account on the same host and get this!
Parse error: syntax error, unexpected T_CONST in /home/sfellows/public_html/wedge/index.php on line 14
and the install stops there?
-
Oh bugger, I forgot that the new install process, since it goes through index.php first, should ensure pre-install.php executions don't run into PHP 5.3-only calls.
I'll fix that ASAP.
Just replace lines 14 and 15 of index.php with:
define('WEDGE_VERSION', '0.1');
define('WEDGE', 1); // We are go.
And yes, it won't help you much... This all means that you're using PHP 5.2 or less, and you need to upgrade/fix your server, or switch to a more competent host.
-
Did the Install Yesterday On a sub-domain/ created DB > uploaded all files via ftp > had all DB info ready, typed in the url and let the install process begin, Install went well no issues, well done!
Note the redirect to install worked great, installed my information > was done in a few!
For those who no not > the info in the form fields during install are on example, you must enter you DB name User db name and passwords you created for that DB, "local host" is the only one you will use! > don't forget to remove the Install.php at the finish of the install, then I would go a head and down load the settings.php to you local disk for back up purposes.
Thanks!
regards,
Maxx
-
Did the Install Yesterday On a sub-domain/ created DB > uploaded all files via ftp > had all DB info ready, typed in the url and let the install process begin, Install went well no issues, well done!
Note the redirect to install worked great, installed my information > was done in a few!
But yeah, this technique was never used in an SMF codebase before, AFAIK, and it makes it much easier to install Wedge from the same package, because then you get to decide whether or not you wish to reinstall (ie, remove Settings.php from the root folder), and it doesn't depend on the package you're using. Also, security-wise, you no longer need to get rid of the install.php file after installing, because it can't do anything by itself. I'd still recommend removing it (I haven't made a full security evaluation on this, and I'm sure there are more people who are more knowledgeable about security than I am), but I'm also tempted to remove the admin warning when it isn't.For those who no not > the info in the form fields during install are on example, you must enter you DB name User db name and passwords you created for that DB, "local host" is the only one you will use!
> don't forget to remove the Install.php at the finish of the install, then I would go a head and down load the settings.php to you local disk for back up purposes.
-
@Maxx localhost is just when you have your mysql server running in the same "environment" of your webserver..
-
Thanks!
Just wanted say it went well!
And also want to direct some of my friends here to check this out, The backup is just in case, I change my mind about where to put, it don't for get, if I have an accident ... getting old LOL! :)
:)
Maxx
-
did a reinstall with the new guidelines. went well
-
I get this message on a fresh install, just after creating the admin account. The message lies across the top of the next screen (i.e. the "Congratulations, the installation process is complete!" step=5 screen). It doesn't stop the installation and is fairly unnoticeable, so it may have been happening a while.
-
Err... What message?
-
:eheh:
Notice: Constant MID already defined in /home/gareth/wedge/install/install.php on line 1391
-
Fixed in the latest version :cool:
-
8-)
-
Nope sorry, I get this error;
35 files for a total of 9 meg were selected and uploaded. No idea what the behavior is on a live site. From what I have read ( Googled ) this seems to be an issue folks have and quite often it is related to a Firewall.
Firefox 26
XAMPP 1.83 / PHP 5.5
Windows 7-64
Flash Plug-in 12.0.0.43
From the PHP.ini file .... default settings
;;;;;;;;;;;;;;;;
; File Uploads ;
;;;;;;;;;;;;;;;;
; Whether to allow HTTP file uploads.
; [url]http://php.net/file-uploads[/url]
file_uploads=On
; Temporary directory for HTTP uploaded files (will use system default if not
; specified).
; [url]http://php.net/upload-tmp-dir[/url]
upload_tmp_dir="G:\xampp\tmp"
; Maximum allowed size for uploaded files.
; [url]http://php.net/upload-max-filesize[/url]
upload_max_filesize=2M
; Maximum number of files that can be uploaded via a single request
max_file_uploads=20
Hope this helps someone. :)
-
« Reply #139 12 hours ago »Last edited 20 hours ago
-
A Time Zone/server issue?
My profile was not set; I then changed it to East Coast/USA and the ' Last Edited' time displayed to me jumped from 5 hours to 17 hours ago. I think I made the post around 7-8 pm USA EST which would be about 5 hours ago. My time for this post is 11:53 p.m, eastern standard time, USA
-
Am unable to install Wedge as a sub-domain to SMF 2.0.7. I receive this following error
Parse error: syntax error, unexpected T_SL in /home/tpforums/public_html/wedge-alpha/core/app/OriginalFiles.php on line 21
this is line 21
http://www.wedge-alpha.mywebsite.net/index.php
Host is Charlottezweb and server PHP is 5.2.17.
What am I doing incorrectly? Thanks :)
-
Re: time zone, how exactly would a different TZ have an influence over the recorded absolute date..? I don't think Modified Date is recorded using anything less than server time... (??)
If yes, it's a bug.
Re: EOS line, well, if you'd read the Requirements stuff, you'd know you need PHP 5.3.
I'm just annoyed by the fact that I keep getting into situations where Wedge doesn't even get the time to reach the point where it says, 'stop! PHP 5.3 needed'... -_-
Anyway, I know for a fact that Charlottezweb supports PHP 5.3, so just switch!
-
re: EOS .... God, I am a dullard. I knew about PHP 5.3 and still had a brain fart and made the post that I made. Sorry about that :)
I have played with the software most of the morning. It really is a nice setup. The Wine theme seems to be my favorite thus far.
-
Really..? I'm planning to remove it actually... :^^;: (To move it to the skins repo definitely, as an example, more than something I'd be proud to have in the default package.)
For instance, what's with this <we:title> styling..?! Wine is the very first skin I built for Wedge, back in 2010, and the goal was to stay within reach of the default SMF theme, Curve, so I kept similar titles. Ever since I finished Wine, I made sure to stay away from these horrible things.
The problem is that I no longer test in Wine, and sometimes you get, ahem, some 'amusing' glitches like blog homepages getting broken titles.
-
I'm liking the weaving best of them, fits better in various situations, and has fresher look and feel, easy to navigate around without distractions.
regards,
Maxx
-
re: skins - Well, all the skins are really good. I prefer the Wine skin because of the color. You did an outstanding job on the color, Nao. A really nice blend of colors that are easy on the eyes. I think that older folks such as myself do not do well with the brighter backgrounds that seem to be popular these days. I think the Wine colors would go well with the Wilde and Wilderless skins.
re: php - well the site was moved to PHP 5.4.24. Still get the same error as before when doing a sub-domain install. I know, I know, you said 5.3 but they moved me to 5.4. :)
Interesting though that Wedge will install on XAMPP with PHP 5.5.6 but would not install as a sub-domain there either.
re: Media - I have found that on Firefox the plugin-container.exe needs to not be blocked in a firewall or to have its dom.ipc fields set to false in about:config. Causes issues with mass uploads, and if streaming vids and uploading with the plugin-container.exe set to false the mass upload may or may not work. Anyway, I am sure some already know that but I did not. :)
-
If by a sub domain you mean wedge.domain.tld then mine is on a sub domain without those issues. Maybe it's the sub domain setup?
-
If by a sub domain you mean wedge.domain.tld then mine is on a sub domain without those issues. Maybe it's the sub domain setup?
If you have any ideas let me know.
Thanks
-
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?
-
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. :)
-
All is good. Wedge is now installed as a sub-domain. Went without a hitch. :)
Patience is a virtue I am told. :)
-
@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!
-
@Maxx(http://wedge.org/profile/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.
regards,
Maxx
-
I downloaded the wedge master zip file from the repo - using the wget command, unzipped and pointed my browser to the wedge directory
it is showing blank page.
-
Same problem/solution as here? http://wedge.org/pub/fixed/8508/installation-problem/msg294738/#msg294738
-
Same problem/solution as here? http://wedge.org/pub/fixed/8508/installation-problem/msg294738/#msg294738
PHP Info - http://54.186.53.116/info.php
Besides, shouldn't httpd.conf (if it's still existing) be overwitten in every server update?
-
Are you sure that your Wedge folder is writable..? What's its chmod status?
-
drwx-xr-x which is 755.
-
Installed after chmod the folder and everything inside to 777 using
chmod -R 777 /path/to/wedge/http://54.186.53.116/wedge/
-
That's because you server marks gz files with the wrong mime type. Did it create the gz/css/.htaccess file or not?
-
Installed after chmod the folder and everything inside to 777 using chmod -R 777 /path/to/wedge/http://54.186.53.116/wedge/
-
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
#
# 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>
-
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.
-
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.
It's not disabled by default. You must remove this option during installation.
You know, I'm running Cherokee :)
-
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.
Thanks.
-
Pandos, it's disabled if Apache is not detected at install time. If it's still enabled, then it's a bug.
Also, it's disabled if you specifically disable 'compressed output' during the install process. It's the HTML page compression feature we're talking about, of course, but Wedge also uses that data to determine whether you want a safe, or an optimized installation.
Wanchope, I looked into your website again (found a few minutes to play with FTP stuff), and noticed that you'd disabled JS compression. I can't help, then... ;)
-
Wanchope, I looked into your website again (found a few minutes to play with FTP stuff), and noticed that you'd disabled JS compression. I can't help, then...