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.
106
Development blog / Re: Alphababy!
« on April 16th, 2014, 05:07 PM »If only I could find someone to implement the rest of my Wedge to-do list for me... Unfortunately I only trust myself for these matters. :whistle:
Everyone can work on it. But you decide if the commits are the way you want.
Sounds good, eh?
How I miss a roadmap... :eheh:
107
Development blog / Re: Alphababy!
« on April 16th, 2014, 10:40 AM »You realize it doesn't take more than a day to get started on a baby, right...? :P
Ah, well, I just couldn't leave a project that's so close to being perfect, could I? ;)
You've got 2 babys then... :)
108
Development blog / Re: Alphababy!
« on April 15th, 2014, 09:06 PM »
Great News!
Congraulations!
Never thought you'd have the time to produce something else than Wedge ;)
No, Wedge is ways ahead in comparision with other forums.
There are a "view" bugs left, but who cares :)
It would be nice if we could implement some features and bugfixing some things before due.
So for me Wedge isn't in Alpha. Great work from a very talented person.
Congraulations!
Never thought you'd have the time to produce something else than Wedge ;)
No, Wedge is ways ahead in comparision with other forums.
There are a "view" bugs left, but who cares :)
It would be nice if we could implement some features and bugfixing some things before due.
So for me Wedge isn't in Alpha. Great work from a very talented person.
109
Archived fixes / Re: Profile Fields Gender can not be displayed
« on April 14th, 2014, 05:43 PM »
Hmm...
Can't reproduce. Even with a complete new install.
Sure all language files are in place and readable?
Can't reproduce. Even with a complete new install.
Sure all language files are in place and readable?
110
Archived fixes / Re: Profile Fields Gender can not be displayed
« on April 14th, 2014, 05:18 PM »
It's the new unisex feature of Wedge :lol:
Just a joke!
Sure your choosen language is in place and readable?
Something in the logs?
Just a joke!
Sure your choosen language is in place and readable?
Something in the logs?
111
Archived fixes / Re: Broken Privacy Topic
« on April 14th, 2014, 03:10 PM »
Just a thought...
What if someone is reporting a private topic to moderator or admin?
How to take action when they can't see it?
What if someone is reporting a private topic to moderator or admin?
How to take action when they can't see it?
112
Archived fixes / Re: Broken Privacy Topic
« on April 14th, 2014, 03:03 PM »
The only way I can think of to get it working is to encrypt private topics AND PM's in DB.
113
Archived fixes / Re: Broken Privacy Topic
« on April 14th, 2014, 02:58 PM »
You can't compare Apples PM's with Eggs Forums.
They are from a technical point of view completely different.
So this is the legal situation in Germany:
The admin of a forum is fully responsible for the contents of his forum.
It's a natural fact that you can see all postings as admin in a forum. Therefor you are responsible for them.
Funny, because you can't read them, when you claim to have topic privacy.. :)
PM's take the status of Mail, Letters, etc.
It's forbidden to read them. So you can't get prosecuted for contents.
Funny, because you'll have the possibility to do that with PHPMyAdmin, etc. :)
Even if you claim to have a software that doesn't support reading of private topics, it's just a forum in the eyes of the law.
They are from a technical point of view completely different.
So this is the legal situation in Germany:
The admin of a forum is fully responsible for the contents of his forum.
It's a natural fact that you can see all postings as admin in a forum. Therefor you are responsible for them.
Funny, because you can't read them, when you claim to have topic privacy.. :)
PM's take the status of Mail, Letters, etc.
It's forbidden to read them. So you can't get prosecuted for contents.
Funny, because you'll have the possibility to do that with PHPMyAdmin, etc. :)
Even if you claim to have a software that doesn't support reading of private topics, it's just a forum in the eyes of the law.
114
Archived fixes / Re: Broken Privacy Topic
« on April 14th, 2014, 02:10 PM »Should admins be able to access topics that are off-limits to them..?
Admins
115
Archived fixes / Re: Broken Privacy Topic
« on April 13th, 2014, 06:33 PM »Not worry about the extra query? It takes about a millisecond on my local install. (Still, I find it 'too much'.)
116
Features / Re: Plugin revs
« on April 11th, 2014, 09:16 AM »
Just a remark...
Don't rely to much on .htaccess because of other servers than Apache that don't support these.... :)
Don't rely to much on .htaccess because of other servers than Apache that don't support these.... :)
117
Archived fixes / Re: HTML5 validation report
« on April 10th, 2014, 02:50 PM »
*lol*
Just a view minutes ago I added a comitt to this on GH :)
Code: [Select] https://github.com/Pandos/wedge/commit/5351e1fc59ad8badb2f176da2ea50e338efb0d31
Just a view minutes ago I added a comitt to this on GH :)
-<head>', empty($topic) ? '' : '
+<head>118
Archived fixes / Re: follow_me() bug, shows up from time to time.
« on April 10th, 2014, 02:24 PM »
Seems to be fixed :)
119
Features / [Poll] Re: Board status icons: what's the point?
« on April 10th, 2014, 09:06 AM »
OK, just a simple comparison.
First the new query with indexes:
Code: [Select] Quote Now see how it's used:
Code: [Select]
OK, let's take a look at he actual query:
Code: [Select] Quote Now how it's used:
Code: [Select]
I think we should give it a try.Quote Yes, but to get the index begin to work you'll have to post one NEW message :)
If you want to stick with left joins, we could try to adding new indexes to DB.
Because the difference isn't that much. Isn't it?
First the new query with indexes:
SELECT COUNT(DISTINCT m.id_msg) AS co, m.id_board
FROM wedge_messages AS m
WHERE m.poster_time >= (UNIX_TIMESTAMP(NOW()) - 30 * 24 * 3600)
AND (
m.id_msg >
IFNULL(
(SELECT lt.id_msg FROM wedge_log_topics AS lt WHERE (lt.id_topic = m.id_topic AND lt.id_member = 1)),
IFNULL(
(SELECT lmr.id_msg FROM wedge_log_mark_read AS lmr WHERE (lmr.id_board = m.id_board AND lmr.id_member = 1)),
0
)
)
)
ORDER BY id_board DESC in .../gz/app/Subs.php Zeile 1390, beträgt 0.00048804 Sekunden bei 0.05243492 der Abfrage.
id select_type table type possible_keys key key_len ref rows Extra
1 PRIMARY m index m 17 2 Using where; Using indexOK, let's take a look at he actual query:
SELECT COUNT(DISTINCT m.id_msg) AS co, m.id_board
FROM wedge_messages AS m[color=black]
LEFT JOIN wedge_log_topics AS lt ON (lt.id_topic = m.id_topic AND lt.id_member = 1)
LEFT JOIN wedge_log_mark_read AS lmr ON (lmr.id_board = m.id_board AND lmr.id_member = 1)
WHERE m.id_board IN (1, 2)
AND (m.id_msg > IFNULL(lt.id_msg, IFNULL(lmr.id_msg, 0)))
GROUP BY m.id_board
ORDER BY null in .../gz/app/Subs.php line 1383, which took 0.00051093 seconds at 0.05717301 into request.
id select_type table type possible_keys key key_len ref rows Extra
1 SIMPLE m ALL PRIMARY,id_board 3 Using where; Using filesort
I think we should give it a try.
But Wedge (and SMF) ALWAYS have at least one post at install time..?
If you want to stick with left joins, we could try to adding new indexes to DB.
Because the difference isn't that much. Isn't it?
120
Features / Re: Cookieless domains and other things...
« on April 9th, 2014, 12:37 PM »JS must be added before the closing body tag, so I'm doing that. The JS files, however, are loaded in the header as soon as you've loaded at least one page. (First page = load at bottom to make page load quickly, second page = load at top because it's already cached so it won't stall loading, and JS features will be available sooner to the user.)
CSS is normally NOT mandatory to render the page, so it's loaded async, and I'm not getting while Google has a problem with that. Anyway, I don't see a problem with loading the CSS at the end, it's just that link tags are usually... at the top. Dunno if it's even valid HTML.