20 replies to this topic

[Philip]

The PHP Freaks team would like to wish everyone a happy New Years, and welcome in 2013 with a bang!

With this new year brings many changes to the main site & forums. We have a lot in the works:

• A new main site, completely redesigned from the ground up.
• An updated forum skin to match the new main site (integrated)
• A premium membership, with a job board, private forums and no ads
• New articles, tutorials and more!

We'd love to get some input from you guys on what you'd like to see change around here. Have a great idea or like something from another site that you really like? Suggest it and help make 2013 a great year for PHP Freaks!

[Pikachu2000]

And a new IRC server too!

[Philip]

And a new IRC server too!

Indeed! And that should be going live soon

I guess nobody else has any wants for the site... must mean we are doing something right! 

[bashy]

• Make the list of "New Threads" longer and maybe add "Latest Replies" section
• Do you have the update from IPB with the best answer in it? I see solved prefixes but in the thread it doesn't give the best answer link at the top. Maybe add that?
• Something along the lines of "Unanswered questions" tag in the menu that gives you a list?
• Maybe add this hook so people can see if the person is still online or not (quickly of course, as it's in the profile card hover) http://community.inv...atus-in-topics/
• Do something with the top advert, the square random one which creates a lot of white space

Edited by bashy, 04 January 2013 - 11:51 PM.

[Philip]

Make the list of "New Threads" longer and maybe add "Latest Replies" section

Can you elaborate on this? I'm guessing you're talking about the forum home's right side? 

Do you have the update from IPB with the best answer in it? I see solved prefixes but in the thread it doesn't give the best answer link at the top. Maybe add that?

We have the update available, however we're holding off until they fix a few more things. The latest patch foobar'd the editor and that is a huge part of the forums for us, so we're waiting until it is fixed so you guys have a better experience. However, this will be applied once that is done.

Something along the lines of "Unanswered questions" tag in the menu that gives you a list?

There will be an option to filter by solved / not solved within the forum threads with the forum update.

Do something with the top advert, the square random one which creates a lot of white space

Yeah, once we migrate to the new skin this should be fixed. I agree, as of now it's not the prettiest.

[bashy]

Yeah the sidebar part, looks a little lonely there on its own
So most of the stuff will be in the update, nice.

Also added another suggestion, number 4.

[Christian F.]

I've only have two suggestions, at least that I can think of at this very moment:

• Fix the bugs I've reported. (Yes, the "rich text" editor is considered a bug. )
• Make the "new reply" link a bit bigger/easier to hit, as the current little blue circle means it's very easy to miss it.

Edited by Christian F., 07 January 2013 - 05:55 AM.

[Philip]

I've only have two suggestions, at least that I can think of at this very moment:

• Fix the bugs I've reported. (Yes, the "rich text" editor is considered a bug. )
• Make the "new reply" link a bit bigger/easier to hit, as the current little blue circle means it's very easy to miss it.

Most, if not all, will be fixed with the forum upgrade + new skin

[kjetterman]

Exciting changes to come! Thank you for the update!

[Christian F.]

Got a couple more bugs, btw. Don't know if they've been reported yet, but...

When editing a post:

• Double clicking to select a word does not highlight it. Or rather, it gets selected for about a fraction of a second, before the editor oh-so-helpfully places the cursor at the position of the last click, and thereby removes the selection of the word.
• If the edit-box has a scrollbar, and is scrolled to the bottom, whenever you click in the editor window it will scroll up a few lines. Making it impossible to use the mouse to select, or navigate to, anything at the bottom of the post. You have to use the arrow keys.

[Philip]

Double clicking to select a word does not highlight it. Or rather, it gets selected for about a fraction of a second, before the editor oh-so-helpfully places the cursor at the position of the last click, and thereby removes the selection of the word.

I can't replicate this, so I'd imagine its a bug with the browser / CKEditor. Can you see if it does it on http://ckeditor.com/demo too?

If the edit-box has a scrollbar, and is scrolled to the bottom, whenever you click in the editor window it will scroll up a few lines. Making it impossible to use the mouse to select, or navigate to, anything at the bottom of the post. You have to use the arrow keys.

Again, don't have this issue over here on Chrome / FF - Can you check on CKEditor's website? If it doesn't happen there, let me know.

[bashy]

The editor on IPB is pretty bad anyway but;

type words -> press bold -> type words -> backspace = WUT

[Philip]

Yeah, I've been working closely with IPS to find other bugs and such in the newest version of the editor (not yet released). Hopefully a lot of these woes will go away then... Or I'll just force you all to use markdown

[Christian F.]

Just tried on their demo page, with and without "source" view. Was not able to reproduce.

As always, my browser info:

Version Opera 12.00 
Build 1467 
Platform Linux 
System x86_64, 3.2.0-35-generic 

Browser identification
Opera/9.80 (X11; Linux x86_64; U; en-GB) Presto/2.10.289 Version/12.00

I should probably note that I always keep the rich-text editor turn off, and I only see this when editing a post. Making a new post does not cause the above bugs to trigger.

Edit:
Neither does it when I'm resizing the editor to provoke the scrollbar.

OK.. Now I can't provoke the last bug at all. :\ I'll let you know if I find a post which triggers it. The first one (double-click select) still happens with this post.

If I use the "full editor" it works as intended, at least with the double-click selection. Not sure about the scroll issues, as I haven't been able to reproduce that yet.
Annoying, as it seems I encountered it on an almost daily basis before.

Edited by Christian F., 11 January 2013 - 12:11 AM.

[kicken]

One issue I've notice with the editor is that it always seems to quadruple my spacing whenever I paste something into the editor.  Only happens around blank lines.  Any idea if this is fixed in an upcoming IPB update?

For example, this is what I type into Edit+ (Fixed spacing to match)

class MyClass {
   public $a;
   private $b;

   public function __construct(){
   }

}

When I paste it into the editor though it comes out like this:

class MyClass {
   public $a;
   private $b;




   public function __construct(){
   }




}

[Philip]

One issue I've notice with the editor is that it always seems to quadruple my spacing whenever I paste something into the editor.  Only happens around blank lines.  Any idea if this is fixed in an upcoming IPB update?

[Philip]

Also, we have the option of using GeSHi / SyntaxHighlighter; I created 2 hooks for those

GeSHi:


SH:


I'll be updating them to include ways to view raw / ZeroClipboard for copy/paste, and a few other things.


Also planning on finding a way to include a syntax highlighter in the textarea as you type - similar to what you see on jsfiddle.

[kicken]

Also planning on finding a way to include a syntax highlighter in the textarea as you type - similar to what you see on jsfiddle.

Could be nice, so long as it works good.  JSFiddle's attempt to highlight/auto-indent stuff generally causes more trouble than anything else for me.  Dunno if it's just a chrome issue or what but it seems pretty buggy.

[Christian F.]

Don't know if you've already tried, Kicken, but I find the input to work a WHOLE lot better if you turn off the Rich-Text editor.

By the looks of your example, it might seem like the editor is having issues with windows-style newlines, causing it to insert double up with newlines, which in turn gets converted to double (or quadruple, if your above example is the actual result) the amount of <br> tags by the editor.
Can't guarantee that I'm right about this one though, as I'm just guesstimating here. However, most of these types of problems I've encountered has been due to incorrect handling of windows-style newlines.

[kicken]

I do use the editor with the rich-text stuff disabled.  Does not seem to matter one way or the other though, the same thing happens.  I'm not sure what is going on with it to cause the problem.  Windows-style line breaks may be a possibility.  It is odd that it only happens with blank lines though and not every line break.

It looks like it's probably fixed in the next version though.  We'll see.