aerynlynne

Thanks for your suggestions proximity! I appreciate the help. ??

But, actually yeah – I may just have stumbled onto Pods very recently (ie this past Monday), but I already love using Pods, lol. It’s enabled a type of versatility to my wp site that I never thought could be easily achieved.

I’ve used MU in the past for other projects, but that’s not the best choice for what I want to do with this site – I’ll be doing quickie reviews on each coffee shop I visit, so each shop won’t need it’s own site for this. Categories would become way too complicated whereas Pods just automatically builds up a database with each entry I fill.

I did get CFT to create the line of code that I would need to include Pods into my posts, but the code is being generated into the Visual editor instead of the HTML editor. :\

What I could do though is just have CFT keep the code string on hand and then I’ll just have to manually ctrl+C/ctrl+V it into the HTML editor each time I require it…

Yep! Spoke too soon! So while this quick-fix works beautifully for the front end of your blog, it does nothing for the back-end. Ie. a lot of errors popped up.

So instead of the one-liner (immediate entry above), the bottom part of the wp-config.php file that begins with: /** Absolute path to the WordPress directory. */ should stay in that file. DON’T MOVE IT.

Also, the include line needs to be a little more literal instead of using the “../”. Your file linking should begin with something like <? php include(home/your-root-folder-name/your-newly-renamed-wp-config-file.php’);

But don’t close with the ?> because you’ll have remaining coding below that needs to be accessed.

So yeah, I just had one of those three-hours-of-looking-for-an-extra-“.” moments once more.

Onto the next day!

*blinks* Well this thread went downhill pretty quickly. Isn’t this the place for users of all capabilities should be able to get “support”? Maybe some of us had a bad day; it happens.

Thank you @a_johnson for providing the link! It was rather straightforward and is one of the few “hacks” that worked for me right away (instead of slaving for three hours trying to find that one little [SPACE] entry that screws up all the coding, heh).

If those of us with shiny new learners-permits can recognise that there might be a potential security flaw in having your usernames/passwords sitting in a php file, what happens when some stealth hacking guru decides to try to ef-ur-stuff-up?

So yes, for fellow newbies/nubes, simply copy and paste the wp-config.php file into the root folder (the one that should have folder names such as: “www”); rename it if you wish, then create a new wp-config.php file to sit in the wordpress folder. This new file should only have one line:

<?php include(‘../your-newly-renamed-wp-config-file.php’); ?>

And this will hopefully ensure that no one can access your wordpress configuration info. Mind you, my knowledge of website security is lacking, so perhaps someone will knock me down an inch or two for trying.

Stay tuned.