Location: WPCAPI.generateCellID

Discussion: url encoding of generated idReported This is a featured thread

Category: Discussion Forum / General Discussion
Showing 2 posts

cpatni
url encoding of generated id
Jun 1 2008, 10:01 PM EDT | Post edited: Jun 1 2008, 10:01 PM EDT
Is this method is required to return url safe ids ? For example if the id is "foo bar", should it return "foo bar" or "foo+bar"? Do you find this valuable?    
ryan_wetpaint
ryan_wetpaint
1. RE: url encoding of generated id
Jun 2 2008, 12:15 PM EDT | Post edited: Jun 2 2008, 12:15 PM EDT
There is no restriction on the IDs returned from generateCellID. You should return the string that exactly represents the ID you intend to use. If our client application needs to use the cell ID in a URL, it will encode it before doing so.

That said, we discourage spaces and encourage hyphens in IDs. Cell IDs are often be used in URLs to reference user-generated pages and hyphens are better interpreted by search engines than encoded spaces. However, if this cell ID is not intended to be used in the WPCAPI.generateCellURL method, then it doesn't matter at all.
 Do you find this valuable?    

Related Content

  (what's this?Related ContentThanks to keyword tags, links to related pages and threads are added to the bottom of your pages. Up to 15 links are shown, determined by matching tags and by how recently the content was updated; keeping the most current at the top. Share your feedback on Wetpaint Central.)
NOTICE CellService CellService.getCellContent
UserService TagService.tagSearch WPCAPI.onpagecreate
WPCAPI.generateCellURL WPCAPI.onpagedelete Function Overriding
WPCAPI.generateCellID EasyEdit hangs sometimes Javascript errors in IE6 and Opera 9.51