will the dde not support paths in filenames and images like /directory/test.jpg ?
Subject: we should support that
will investigate the issue!
thanks!
Subject: Is this going to be fixed in 8.5 gold [EOM]
Subject: Did this ever get reported? A bit worse in 8.5.1
The workaround that I found (see elsewhere in thread) still works somewhat, but it seems like 8.5.1 is complaining more about it even though once you get the element created with a “/” in the filename, it works.
This is beginning to make me a bit nervous. Our entire Notes-based CMS that drives 4 web sites relies on having “/” in design element names. Getting rid of it would be like having a web server that “doesn’t do directories”.
Subject: Still doesn’t appear to be supported in 8.5 production release
I tried creating several different types of design elements using the “/” as part of the element name. Several of them worked (views, forms, pages, etc.), but the following still do not support this:- File resource
-
Image resource
-
XPage
-
Stylesheet resource
-
Custom control (may not be a big deal in my case)
As I mentioned in this thread almost a year ago, this is really a deal-breaker for mine and other web applications. The / character is used in the element’s name because of how browsers handle relative URL’s and base URL declarations.
In the case of XPages, I can see where not allowing it doesn’t break backward compatibility because you won’t have existing XPages out there with /'s. Not so with file, image, and even the existing css resources.
Subject: There does appear to be a work-around, but only minimally tested
If you create the design element without the / and save it, then you can select it the design element from the Applications sidebar or from the design elements view (for example, “Style Sheets” - listing them all in the main content pane).
Below the main content pane there is another pane with a Properties tab. Under basic properties, you can replace the name/alias and include the / character.
So, it appears to be a limitation of the box where you initially enter the design element’s name, rather than a pervasive limitation of how the whole feature is implemented. That’s just a guess, though.
Subject: Any way to open classic mode? Like the notes client?
Subject: HUGE problem
This is a SHOW-STOPPER right now and means I have to uninstall 8.5 and reinstall 8.0.1.
Images, files, stylesheets cannot contain / characters in them.
I have tried to create a new file (New File Resource) and am prompted “Invalid file name”
If I look at resources that were created with 8.0.1 and before, they show correctly in an older designer client, but in the new client, only one (incorrect) entry is shown in the list, that is the folder name.
Clicking this generates an error.
An example - use a pre-8.5 designer client, attach images, rename them images/a.gif and images/b.gif
Go into the 8.5 designer client - you will see ONE file resource called images. Clicking on this generates an error. a.gif and b.gif dissapear!
I use pseudo-folders in filenames all the time, in all applications, to separate various frameworks and for lots of other reasons, in web apps.
Subject: Its a show stopper allright
I have just hit this show stopper today as well. Installed 8.5 this morning, and just uninstalled it this afternoon as well!
Unless this is resolved, we would be unable to use the 8.5 platform for development at this time
Subject: Show stopper here as well…
This will break a lot of web applications because we count on being able to use the / character in URL’s to simulate directory structures and control how things like relative URL’s, the base tag, and things like that are interpreted.