Support Forum
Support Forum
Offline
As long as you don't upgrade your theme the changes will remain. You can tweak it and before you upgrade convert the one you are using to a custom theme. That way you don't have to edit a newly released theme when upgrading.
You can then add anything that may be new, and something you want, to your old theme. All the theme changes from what is current now to what is changed/added in a newly released theme will be documented. That way you can compare the new with the old easily.
Custom Simple Press Themes
Offline
Sounds good Brandon. Preciate it. We will see how long I can stay with these changes before having to worry about upgrading. I was thinking that I might just be able to swap out the default.php files after an upgrade, but the more I thought about it, the more it would probably conflict with other potential changes that could happen during an upgrade that are unrelated to css concerns... Normally that's how I would do it, but when the php and css are so closely integrated in a plugin such as this, it would be wise to take extra steps to insure a safe upgrade. Any thoughts?
John 3:16
Offline
Any update to the Simple:Press core plugin does not require that you update your theme. When a new theme comes out it there can be several reasons for it. New options, bug fixes to take advantage of a new SP plug in. That's why the changes are documented so you can see what was changed. If a bug fix like what we just released for the iForum theme then you would want to include those changes in your theme. If the changes are for features you don't need or want you can stay with your old theme.
For example there will be some changes to the next new theme's to allow adding nofollow to links in the user info area of topic view. Like the twitter logo. If that is something you don't care about then you don't need to add that to your theme.
I still recommend you create your own theme though. That way when you are editing your theme if anything goes wrong and it doesn't work you can revert back to a default theme while you diagnose and fix the problem.
Offline
Good advice. Thanks man. I will keep that in mind for when when I am about to launch the site. Probably be something I do a couple days before going live. Will have to dig into the documentation on it, and I really just don't have the time right now.
Editing wordpress login page templates can really be a bear... Especially when you thought you could just redirect it completely to begin with... but turns out I need to keep it active in order for a specific plug which blocks bum registrations to work. Luckily theres another plugin out there that makes editing the default login page doable in a more intuitive manner... but the css is still pretty lame, hah. Plus, my edits are very obscure... Its not so much I need to edit it, as just cloak the whole darn thing. lol. Luckily the plugin saves all changes to a separate css/problem-with-post-edit-buttontml file within the plugin so no upgrades will reset it. Yay.
Anyway, got it done. I'm ranting cuz I'm tired. lol. Goodnight.
John 3:16
Offline
I know what you mean on the available WordPress login page plugins. I decided just to make something myself it was easier than using theirs and then changing it to fit me.
Sounds like you could use a blacklist of disallowed user account names when registering with Simple:Press.
Maybe there is something in the works.... 
Offline
blacklist of disallowed account names and display names coming in next version...
Visit Cruise Talk Central and Mr Papa's World
Offline
Very cool guys. I love how simple press is so ingrained in the wordpress template. I did manage to get my login page wiped clean, lol. It's basically just a background unless a user is activating a new account. It took a "minute or two" but its done now and I am happy with the css and everything. The custom login plugin basically hacks an html and css script into the login form wordpress files. Pretty nifty for those of us who intend to keep the entire registration and login portion of their sites on the front end. Thanks for the heads up on the next version. And yes, the blacklist function will probably be useful in the future. Looking forward to the next version.
John 3:16
All RSS1 Guest(s)