Thread

Yay!!!

fixed_order=”“3|7|1”

I think my dreams have come true!!! 😉

Thanks for the great updates. Again fantastic work from a fantastic bunch of developers.

I suppose my thread for my very very simple redirect plugin can probably be deleted now though :down: 😊

Best wishes,

Mark

After a brief discussion with some of the developers advocating the jQuery extension, I’ve updated the download to reflect the new version.  If you have already downloaded ExpressionEngine 1.6.5, you may also download the jQuery for the Control Panel extension by itself in the add-on area.

Does this mean that i really need to start study that also =) Phew, EE puts me back to school =)
By this i mean the jQuery-part, because i just cant keep my fingers out from it…

Cheers:
- Tuittu

No, it’s only something that developers need to worry about, Tuittu.

After a brief discussion with some of the developers advocating the jQuery extension, I’ve updated the download to reflect the new version.  If you have already downloaded ExpressionEngine 1.6.5, you may also download the jQuery for the Control Panel extension by itself in the add-on area.

So the control extension is now in the download? Excellent, grabbing the 1.6.5+ plus now.
Cool then it uses the Google hosted version jQuery, sounded like a smart idea.

So…you guys might wanna update the EEDocs to include uploading the extensions folder as well 😊

See the 1.6.5 version notes, it’s included there.

I had a feeling it would be today! Not sure why, just did. We’re one step closer to EE 2.0!

“Modified URL title creation to allow dashes, underscores, and periods regardless of the separator preference, and to allow uppercase characters.”
“Modified Wiki URLs to allow dashes and underscores regardless of the separator preference.”

Like Homer Jay Simpson would say: “WOHO!” \o/
Thanks for listening Derek <3

Major overhaul of Auto-XHTML typography. More intelligent, more flexible, and improved performance

What that really means, i would like to know little more details if possible, thanks.

Cheers:
- Tuittu

So if I understand correctly, there are no observable jQuery changes to the CP; it just includes the tools needed for extension developers to add such things later, is that right?

Major overhaul of Auto-XHTML typography. More intelligent, more flexible, and improved performance

What that really means, i would like to know little more details if possible, thanks.

Cheers:
- Tuittu

Well, it means some troubles for me, I have to correct a lot of my entries with auto xhtml formatting. The Auto-Xhtml typography formats your text in an entry in an “intelligent” way, but when you add some extra formatting (“p class=.......” for instance), the system omitts the correct formatting of the following text. I understand we have to be very “correct” now when writting entries. But it’ll be “very profitable investment” in the future.

My question: how to hide the text: “Commenting is not available in this weblog entry.”, added by the system when comments are not allowed for the specific entry?

Major overhaul of Auto-XHTML typography. More intelligent, more flexible, and improved performance

What that really means, i would like to know little more details if possible, thanks.

Cheers:
- Tuittu

Well, it means some troubles for me, I have to correct a lot of my entries with auto xhtml formatting. The Auto-Xhtml typography formats your text in an entry in an “intelligent” way, but when you add some extra formatting (“p class=.......” for instance), the system omitts the correct formatting of the following text. I understand we have to be very “correct” now when writting entries. But it’ll be “very profitable investment” in the future.

The details of the changes are all esoteric except to programmers.  For non-programmers, all you need to know is that your content publishers can more easily mix XHTML and non-formatted text together, and still end with nice looking, valid XHTML output.  The previous system allowed for that with certain tags, but was not comprehensive, and used an expensive method of doing its parsing in comparison to the new.  So, in the change log that translates to: smarter, better, faster.

serafico, you should not have to “correct” any of your entries.  The new system will accommodate pretty much any markup you can throw at it, including using your own paragraph tags with attributes.

My question: how to hide the text: “Commenting is not available in this weblog entry.”, added by the system when comments are not allowed for the specific entry?

If commenting is enabled for a weblog, but commenting has been turned off or expired for the entry, and it is being viewed on a page with a comment form tag, that message will be output.

The programmers who are normal, and the changes, which are esoteric, can be viewed readily in the Typography class.  😛

Essentially it was an adoption of a strengthened version of CodeIgniter’s typography, which grew from EE’s original typography.  It has come full circle, and is greater for its travels.

My question: how to hide the text: “Commenting is not available in this weblog entry.”, added by the system when comments are not allowed for the specific entry?

The string that goes with this text is found in the lang.comment.php file. You could always replace that text with something else.