This week’s round of fixes

by Alexandra in Qt DevNet News (1635 views)

Since Marius is probably lying in the sun somewhere right now, it’s my turn to blog about the latest fixes that went in today. Thanks to everybody who reported bugs. Keep them coming!

And here’s the top list:

  • many registration issues particularly with IE8 are fixed
  • wiki redirections are now possible – check the fields below the input field
  • wiki history support for category pages
  • openID settings available in the control panel
  • sub-category pages in the wiki can now be edited without fiddling with the URL
  • export to pdf now also supports wiki category pages

One issue we discovered today didn’t make it into the roll-out: adding tags when using IE8. It’s an AJAX bug and we’re on it. Good news is that you can add tags with IE8, you just don’t see them appear until you refresh the page. Slightly cumbersome but at least the functionality is there and IE8 users can still earn their points. ;)

And now it’s time for a summer weekend in this part of the world.

3 comments

Picture of Gurudutt

July 16, 2010

Gurudutt, Hobby Entomologist

Hey,

We have fixed the Add tag in IE8 and it works now.
Still if you see an issue please feel free to report us vai various channels.

NB : We are still working on tag search and soon will come back with all fixes.

Happy Summer !

Happy Holidays :)

Picture of Tobias Hunger

July 16, 2010

Tobias Hunger, Mad Scientist

Thanks especially for the redirection feature. I already redirected all the different Qt Creator categories to one page in the wiki:-)

One thing I noticed: When reverting a page back to a previous version “{revision_notes}” ends up in the “describe your changes” field. Shouldn’t that be the actual text of the revision notes instead?

Picture of Gurudutt

July 16, 2010

Gurudutt, Hobby Entomologist

Hi Tobias,

“When reverting a page back to a previous version “{revision_notes}” ends up in the “describe your changes” field. Shouldn’t that be the actual text of the revision notes instead?”

This is in consideration and will be fixed soon.

Write a comment

Sorry, you must be logged in to post a comment.