In what instance are you getting the 'keep_theme'? I only get it when I type it in directly testing new themes I am creating. If I type it in wrong (the theme does not exist) it directs me to the default theme)
Name the theme you want people to see the same as the name of your website and it will default to that. eg. Your site name = your_site_name for your default theme.
In what instance are you getting the 'keep_theme'?
I get it with polls when I click on the vote button, view results link, view all link and view link. I haven't done a thorough check to find all instances on my site. I haven't even finalised exactly what modules I even want to use yet.
Brian Hay said
Name the theme you want people to see the same as the name of your website and it will default to that. eg.
That's exactly what I want to avoid. If there is a theme name in the URL and a user bookmarks the page then in the future when they use the bookmark they will either not see the current theme if I change it (because the URL has a perpetual reference to the old theme), or if I delete that theme when I cut them over to a new theme they will get an error message, which I don't want them to get.
Do you have a Samsung Galaxy S / Galaxy S II ? If so, why not check out my ScreenFree FM Radio .
No, I didn't explain myself well. If someone goes to &keep_theme=does_not_exist they won't get a 404 not found. They will see the page they are looking for with the default theme for your site. The default being ether ocPortal's own default theme or the them that is named the same as your website is named in you configuration if it exists.
Explanation: The poll is in an iframe so voting doesn't do a page refresh (we don't use AJAX for this kind of thing for web standards reasons). The theme is passed to the frame via keep_theme so that it knows what to run (because in theory the poll might run with different themes in different zones). The problem is that then leaks into the links, which is not good. So this fixes it .
If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.