Only managed about 300 more words on Lowborn between the weather and the young one. I’ll shoot for more tomorrow.
I’m at least writing every day ( and avoiding the temptation to code :p ) and that’s far better than I was doing for a while.
Now, to see if this update to WP will go through without crashing *laugh* After that, it’s off to bed with me.
Managed to squeak out another 500 words on Lowborn. About to get to an important little scene that’s going to figure strongly into the ending, and I’m tired as hell, so I’m going to take a break. Would have probably written more, but storms forced me to shut down for a while. Not risking my computer in all that lightning.
At an important ( if not quite so much as the one in Lowborn ) scene in SOTM 18 as well, so I don’t want to work on that while I’m not at my best either.
As promised, I avoided the temptation to code tonight. *laugh* I did sketch out the database table for my “latest releases” so when I’m ready, I’ll have that on hand and ready to create it. Then, it’s a matter of figuring out how to call templates under the new system so I can get the beginning of my back-end functions. There’s examples for pretty much everything else in the new content system, but not for that. I’ll have to dig around a bit.
The slow part is going to be getting back on the coding horse, and learning the basic ins and outs of the new system. By the time I finish with my first back-end + widget, I should be up to speed enough to crank out some content at a much quicker page.
One thing I like about the new system is that I can restrict damn near anything — on any page on the site — by the forum user groups or settings selected in the profile. That will give me the opportunity to do all sorts of things with ease that would be difficult otherwise.
Okay, I’m going to write a little smut in my third pen name, and then hit the sack. Maybe the weather will cooperate to let me write more tomorrow.
Got a little more writing done on SOTM 18 and Lowborn 07.
Then I couldn’t resist popping into the coding a bit. Unlike my last little quest, this one proved simple. I can easily change the logo, display picture, and main page text to either the “warning: adult site!” if you aren’t logged in, or the standard front page of the site if you are.
What that means is that if you stay logged in, you’ll never have to see the warning page. As simple as the process is, setting up the conditionals to filter out nekkid images of either sex or filter all nekkid images ( so you can browse with a little more piece of mind when prying eyes are about ) will be a piece of cake.
I’ve decided that if someone isn’t logged in, it will default automatically to full SFW filtering. If you want to see the pics, you’ll just have to sign up and log in :p
My next coding adventure will be trying to set up a custom database for the “Latest releases”, a back-end utility to update it, and a widget to display it. If that works, then adding content to the website is going to be a breeze once I code the remainder of the back-end utilities.
I do believe I’m going to get my money’s worth out of this purchase 😀
I know. You’d rather I was writing instead of coding, but having the website sitting here as a blank slate for so long has really bugged me. It wasn’t even really getting updated when there was still content available. Having the ability to interact more easily with readers might just inspire me, as well.
Promise I’ll resist the urge to code tomorrow when I get home from work and try to get either Lowborn 07 or SOTM 18 up to a point where I can make a progress report post on them. I just can’t help being tickled that this is working out, because I took a big leap of faith.
Took a break from writing earlier and decided to see if I could get the WordPress “updates” block working with the login block real quick.
Quick didn’t happen.
I’ve been obsessing on the thing all day, and I finally got it working! I had to make some changes to the way my blog displays urls, and then finally screw around with variations of the rss link until it came out right.
Edited all the templates to remove the parts of IPBs templating that I didn’t want, inheriting mine instead, and it finally looks exactly how I want it to.
I’m sincerely hoping that was the hard part *laugh* I know it was last time, trying to integrate the two under the old software. Other than that nightmare, I really like the object-oriented way things are designed in the new software. I have high hopes that I won’t have to modify a single line of code in the actual software package, but instead use the functionality present to create what I need in a way that won’t require crossing my fingers every time I update to new versions.
I can’t begin to describe the feeling of victory I’m having right now *laugh* This is what happens when old coders fall off the horse for a while.
Absolutely not going to fiddle with the conditionals for a little while. I still have to puzzle out the best way to use the widgets in the new software to accomplish this in an efficient manner.
Now, to catch up on some of the writing time I lost while I was obsessing.
So far, it looks like IPB is going to serve my needs perfectly. I’m able to integrate a login into my templates with ease.
Next step will be to make sure my WordPress code will integrate into that, in order to display the updates block. I had problems with that when trying to do it under the old back-end software. Hoping it won’t be an issue again. I suppose that if it becomes a problem, I could always use the Articles functionality of IPB and retype all those bloody entries… again… but I really don’t want to do that *laugh*
After that, I’ll start experimenting with the conditionals — displaying a warning page to anyone who isn’t logged in, filtering images based upon the settings chosen at sign-up ( going to be required, though the default will be no filtering )
Once that’s working, I’ll delve into custom databases and administrative functions. Once I puzzle that out, I shouldn’t have any trouble restoring and updating all the content that used to be here, as well as easily adding to it. Just as going with this blog for updates increased my update frequency, so should having a fill-in-the-blank backend of the site increase the amount of content I’m able to add without much work.
Wish me luck! *laugh*
I’m going to celebrate with a quick break, then write for a while.
