Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Nao
1831
Features / Re: New revs
« on January 24th, 2014, 09:17 PM »
[Commit revision d9c6d22]
Author: Nao
Date: Fri, 24 Jan 2014 21:09:56 +0100
Stats: 1 files changed; +1 (insertion), -1 (deletion)
  • Oops-- typo. (Themes.template.php)
1832
Archived fixes / Re: Error Log
« on January 24th, 2014, 08:50 PM »
Still don't see how you could have executed that code in the first place...
1833
Archived fixes / Re: Errors when going under Theme Settings
« on January 24th, 2014, 05:57 PM »
Well, latest commit removes this theme page anyway. I should have done that in the first place.
1834
Features / Re: New revs
« on January 24th, 2014, 05:56 PM »
[Commit revision 3ff60b1]
Author: Nao
Date: Fri, 24 Jan 2014 16:56:57 +0100
Stats: 1 files changed; +1 (insertion), -1 (deletion)
  • After all these years, Safe mode is still a PITA. (Class-WebGet.php)
[Commit revision 006d159]
Author: Nao
Date: Fri, 24 Jan 2014 17:53:49 +0100
Stats: 2 files changed; +18 (insertions), -11 (deletions)
  • Removed some theme code. (Admin.php, Themes.template.php)
[Commit revision 14cc26c]
Author: Nao
Date: Fri, 24 Jan 2014 17:55:38 +0100
Stats: 1 files changed; +5 (insertions), -5 (deletions)
  • Apparently, for some reason beyond my understanding, the installer's INSERT functions will choke on tables that have text fields, unless you explicitly set a value for these fields (even if empty). I don't get it. But I double-checked, and all other tables were already doing that, so I guess it's a known problem. Buh-bye. (install.sql)
1835
Archived fixes / Re: Log throws errors
« on January 24th, 2014, 05:43 PM »
This would be triggered by a communication issue with the Mentions plugin.

Never happened to me at wedge.org, though...
1836
Archived fixes / Re: Errors from ManageServer.php
« on January 24th, 2014, 05:39 PM »
It was already closed.

Also, this bug was reported by someone else earlier, I was simply waiting for the line numbers to come up -- and there you go, a second identical bug report, and again, no error lines. Not helpful.
So, as such --> I looked into it myself, and it's very likely you got the error on the Cache settings page. Basically, if it can't find a non-file cache system available, it'll try to combine two empty arrays into one, and this generates an error. Problem is, my PHP doesn't spit out any warnings or errors, and yes, I don't have any cache systems either.
Yet, the latest version should no longer exhibit this behavior.

Still, any errors that are reported at least twice = probably something to look into.
1837
Archived fixes / Re: Error Log
« on January 24th, 2014, 05:35 PM »
Code: [Select]
@curl_setopt($curl, CURLOPT_FOLLOWLOCATION, true); // Accept redirects

Or just download the Zip from github again, and overwrite your Class-WebGet file with the new one.
1838
Archived fixes / Re: Themes directory is not writable
« on January 24th, 2014, 05:34 PM »
[iwantthistoblink]WEDGE REMOVED THEME SUPPORT LAST WEEK.[/iwantthistoblink]
YOU SHOULDN'T USE THIS AREA. IT'S AN ALPHA. I HAVEN'T YET REMOVED THESE PAGES BECAUSE I NEED TO CLEAN UP LANGUAGE STRINGS.

If I see another error regarding the Theme Settings area, I'll just remove the post.
1839
Archived fixes / Re: Errors when going under Theme Settings
« on January 24th, 2014, 05:32 PM »
Will you PLEASE read other topics before posting your 'errors'..?!
1840
The Pub / Re: Wedge repo -- installation feedback
« on January 24th, 2014, 05:31 PM »
Quote from Norodo on January 24th, 2014, 03:41 PM
I've managed to install Wedge somewhere, finally. It's on my laptop localhost. I did get this error message while installing:

Code: [Select]
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
And again:
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..?
Quote from Norodo on January 24th, 2014, 03:41 PM
Code: [Select]
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.
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.)
Quote from Norodo on January 24th, 2014, 03:41 PM
I also got this after opening logs:
Code: [Select]
8: Undefined offset: 0
File: /Users/Finn/Sites/wedge/gz/app/Subs-BoardIndex.php
Line: 472

All in all it seems to work!
Any reasons why Wedge should fail to find any board category..?
On what page are you getting these errors, exactly?
1841
The Pub / On refactoring the installer flow...
« on January 24th, 2014, 05:17 PM »
Quote from havok on January 23rd, 2014, 03:00 PM
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 was actually working, a few hours ago, on making the install process easier for everyone.

The idea is to:
- ship Wedge WITHOUT these folders: /attachments, /media, /install/Settings.php, /install/Settings.php.bak
- modify index.php so that on each page load, it checks for these files. If it finds them, cool. If it doesn't, it actually recreates them from scratch, not from an existing file or folder, but simply by creating files and writing text to them. (Yes, it works fine. And it avoids the eternal problem of ensuring these folders are all writable.)
- if Settings.php isn't found, run the install process.

This is pretty great. But causes three major problems to me.
  • By running the install process, I *thought* that it would be simple to just include /install/install.php, but in fact it's more complicated than that, as Wedge expects the installer to be in the root... So, I'll probably (?) have to copy the install.php file to the root automatically, and then run it from the root.
  • More importantly, what happens if someone else visits your empty website after you uploaded it by FTP and before you went to the root? Because the Settings.php file was already re-created, you'll just find an error page because the DB data is wrong, while the other visitor will be presented with the installer tool. Meh... Of course, not possible.
  • I don't know if I should be wasting time making multiple folder/file existence tests for each page load: the aforementioned files, but also generally the /install folder. If it's found while Wedge is up and running, should we attempt to delete it..? And if it fails, does that mean Wedge will permanently try to delete that folder on each page load...? :-/
Opinions welcome, really.
1842
The Pub / Re: Wedge repo -- installation feedback
« on January 24th, 2014, 05:08 PM »
Quote from ftab4me on January 23rd, 2014, 09:41 AM
Quote from Nao on January 22nd, 2014, 09:44 AM
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:
"Read me files, we don't need no stinking rename filed"
Apparently, you don't need proper quote tools either, eh..? I've fixed your post for you.
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.
Quote from ftab4me on January 23rd, 2014, 09:41 AM
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.
Nah, I don't need to test anyone's site, I'm already overwhelmed with just wedge.org and my local site...
Quote from ftab4me on January 23rd, 2014, 09:41 AM
Please change my login name to wedge.helmerl.co might as well keep things consistent!
You can do that yourself, if you wish...

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.)
1843
The Pub / Re: Wedge repo -- installation feedback
« on January 24th, 2014, 05:03 PM »
Quote from Wanchope on January 22nd, 2014, 06:47 PM
The part to the theme in the theme settings is wrong, it says website.com/Theme; this is not a correct part.
Theme settings..?
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.
1844
The Pub / Re: Wedge repo -- installation feedback
« on January 24th, 2014, 05:01 PM »
Quote from Norodo on January 22nd, 2014, 06:05 PM
I'll get a testing setup done and give you the details over PM sometime after dinner today.
Thanks, I'll have a look ASAP. A bit overwhelmed after taking a break yesterday...
1845
Archived fixes / Re: Error Log
« on January 24th, 2014, 04:56 PM »
Hmm... Try putting a @ before that instruction..?

I'll do that on my side. Unfortunately, I'm not willing to 'fix' outdated servers. The alternative is to add 50+ lines of code and test it. I've never touched that file, and probably never will. (Me, lazy. Or simply, me tired.)