Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

Archive /

Our old forums are still available as a read-only archive.

Moderators: martimiz, Sean, biapar, Willr, Ingo, simon_w

2.2.1 Changes - Hyperlinks in IE and Reordering the tree


Reply


5 Posts   1139 Views

Avatar
Aaron

Community Member, 63 Posts

20 March 2008 at 3:17pm

Hi there,

We have a client whose site was developed in using an older version of SS but was upgraded before launch.

I wasn't the developer in charge of this one, so this is mainly my first exposure to the system as the other developer is away for a few weeks.

Our client has raised two questions about things they have noticed change in the upgrade:

1. In IE7, when adding content to a page - If you go to add a hyperlink by selecting the text and clicking the "chain" icon in the editor, you get the link toolbar popup on the right. As soon as you set the focus of any control in that sidebar, the text in the content box is deselected. This makes adding hyperlinks totally impossible and seems to be a bug. It works fine in FF, and I have installed a fresh copy of SS as a test, and the problem still exists in default setup.

2. They claim that before, drag and drop reordering was possible on all items in the tree (I havn't seen the old version so can't confirm). But now, you can only activate reordering when creating a new page it seems. Am I missing something? It seems a bit silly to be only able to reorder existing pages by creating a new one, so I'm guessing I am missing something.

Any help with the above two?

Cheers
Aaron

Avatar
Aaron

Community Member, 63 Posts

25 March 2008 at 10:36am

Really? Noone else has come across these issues? Or is the community for this particular CMS largely inactive at the moment?

#1 seems to be a pretty bad bug so I am very surprised if no-one else has had this problem, although I can find nothing in the Bug Tracker or forums. I have downloaded and installed 3 copies of SS and all have the same issues.

Avatar
Fuzz10

Community Member, 787 Posts

25 March 2008 at 11:26am

#1 is indeed a huge bug. As a matter of fact, I advise my clients to use FF for SS work anyway, because IE7's javascript performance sucks so friggin'hard.

Seems there's already a patch for it :
http://open.silverstripe.com/changeset/51081

#2 will be resolved in version 2.2.2 (check out the latest RC)

Avatar
Liam

Community Member, 470 Posts

25 March 2008 at 11:31am

I just tested on a development install I have and can confirm the issue even with the latest rc version.

The community isn't super active by any means, so at times it can be frustrating when waiting for feedback.

Personally I love the concept of SS and a lot of the fundamentals of it, but I can't deploy it on a live site for any of my clients. There are numerous issues with it like this, and performance isn't up to par with my expectations. I have no doubt that in the future I'll be using it, but I've been playing the waiting game for the past few months. The latest rc build is getting there, but not quiet yet.

Avatar
Aaron

Community Member, 63 Posts

25 March 2008 at 11:50am

Edited: 25/03/2008 12:09pm

Thanking both of you.

LeeUmm - thanks for the heads up on community activity. I was curious as this is my first outing with the system and on these forums.

I spent a small chunk of the easter weekend doing SS tutorials and I have to agree with what you say about the concept of the SS system. I come from a Drupal background and Silverstipe's datamodel just seems to be a pleasure to use for building custom plugins in comparison so far.

The backend is a winner too. Many of our clients have been Joomla users in the past and they are largely blown away with the SS admin. (except for a few comments on speed - 50+ JS files doing all that pretty work)

Fuzz10 - I recommend FF to absolutely all clients, however some are not in a position to switch, most are simply resistant to change. In fact I've only ever been able to fully "convert" one client in 5 years of web dev.

I will try that patch, and checkout 2.2.2, and failing that - insist to the client that FF is the only option in the interim.

[edit] Did ask about #2 again but then re-read Fuzz10's post[/edit]