Tips and Tricks: Creating new Custom Pages in TeamRaisers with specific SID/SOID

Mark Kindy

So, I haven't seen this mentioned anywhere in documentation or on this forum, but I made a discovery awhile ago that helped me out when a problem with a Blueprint meant I had a selection of pages in a set of TeamRaisers that turned out to have different ID numbers assigned to them.



When you click "Create a new Custom Page," you'll be taken to a page whose URL resembles this:



.../TREdit?soid=0&page_type=fr_informational&tr=create_informational_page&action=create_informational_page&fr_id=99999

Knowing that "soid" corresponds to the ID number of the given custom page, and that Luminate uses "0" in specific contexts, I presumed that "0" tells the editor to assign the page we're creating the next available ID number.  On a whim, I changed the number assigned to soid in the URL and pressed enter so as to reload the page with the new URL, like so:



.../TREdit?soid=<span style="color:#FF0000;">12345</span>&page_type=fr_informational&tr=create_informational_page&action=create_informational_page&fr_id=99999

The page reloaded and didn't look any different, but upon saving the page, the editor assigned the new page an ID of 12345.  Doing this, I was able to work around the headache of rebuilding a bunch of sites from Blueprint.



I don't believe there are any restrictions on what the number can be (except, maybe, a signed 32-bit MAX_INT?), and though my experience has been that it will not overwrite an existing page, best to double-check that the ID number you want to use isn't already in use.



EDITS: To fix display of <code> segments.

Brian Mucha

I discovered this a few years back, but tried it again recently and it didn't work so I thought that trick was done. Good to see I just screwed it up.



Great post!