Store Locator Plus

I’m getting ready to install a plug-in that enables visitors to a client site to find what they are looking for. I was envisioning this to be a difficult process, but then I found this gem: http://tx.ag/ru7hjk

Initial Setup & Thoughts

I installed the theme without incident. I added in a few spots, set a few options, selected the “Big Map Rev 01” theme, and it’s ready to boogie with minimal tweaks.

It took me a moment to figure out that I needed to create a page in “full width” layout, and that the short-code needed was simply [ SLPLUS ] (no spaces). That wasn’t overly clear in the directions, but not hard to figure out either.

The admin panel is well laid out, easy to use, and has those fabulous question marks to pull out extra info for you when needed. I like it.

[Tweet “Find what your looking for with the Store Locator Plus (WP Plugin)”]

Little Blips

The styling of the theme has some oddities that need fixing, and the formatting of the address in the map bubble is very clumsy. Lastly, I don’t readily see where I can change the default radius to 10 miles instead of 200.
Read More

Importer Not Functioning

I have loads of posts, but the WordPress importer doesn’t like WordPress 3.9.1 in the slightest. Hopefully, they’ll resolve this soon. This importer has worked famously up until now. I tested a few other importers, and nothing is working with the file that WordPress exported (in WordPress format). Well, that’s a little frustrating.

[Tweet “The WordPress Importer plug-in is not working with WP 3.9.1 @WordPress”]

The plugin: http://wordpress.org/plugins/wordpress-importer/

My post in their support forum:
http://wordpress.org/support/topic/upload-doesnt-happen

Update 6/25/14: There’s one response to my support forum post. At least I know I’m not the only one!

My next step is to turn on debugging. If that doesn’t result in any clues, then I’ll export the blog in a different format (CSV, perhaps) and try a different kind of importer. If THAT doesn’t work, I’ll just have to move the posts manually (ugh). Thankfully, this is a fairly unique circumstance at this point. However, I’m surprised that it isn’t easier to export and import to and from WordPress. It should be.

Update 7/17/14: I gave up on the WordPress Importer when I found this article: “Best 10 Free WordPress Plugins.” I installed the WP CSV plug-in on my old blog, and installed the Really Simple CSV Importer plug-in on this blog. That did the trick!

Now to clean things up a bit around here.

Adding a Search Page to a WordPress Website

One of my sites doesn’t have a search box on the home page, and we wanted to go about offering an easy search option. I found this incredibly helpful article: http://codex.wordpress.org/Creating_a_Search_Page — I followed the directions listed under “Using the page.php” heading.

A few notes regarding the posted directions: The first step says to save the file, but not where. Save it to the themes directory under wp-content. That’s where you will upload it in the end. I keep a mirror of the website on my hard drive (makes things like sync’ing files and such a lot easier).

Secondly, you uploaded the new search page template… now what?

Go to the Pages manager, add a new page, and select “Search Page” from the template drop-down under Page Attributes. You’ll find the page attributes module on the right-hand side of the page.

Lastly, there’s no need to add any content to your new search page – it won’t show up. If you want the search page to look/feel different, head over to the Editor (under Appearance), select the searchpage.php file you created, and edit away.

For example, I went back in and choose a different page template from which to base the search page template on. The theme this site uses has a full-width page template that I liked better for this type of page. That was a quick fix tho – same instructions, just replace a different content loop.

White Screen of Death

This fun little problem has occupied me for long enough that I figure it’s time to blog about it. Who knows? It might help someone else!

I’m installing WordPress  into a sub-folder of the root. I followed the 5-Minute install directions, and when I ran the install.php file, it gave me bubkis. This isn’t my first time at the WordPress installation rodeo, but it is my first “White Screen of Death.” Awesome.

Stuff that Does NOT Work

I found the following steps on various web pages, and none of them worked.

  1. Add an .htaccess file to the subdirectory to make sure WP knows to go to index.php.
  2. Remove extra blank lines from the beginning or the end of the code.
    This advice was given A LOT and it didn’t make sense to me at all. Why would that work?!
    I tried it anyway, and much to my relief, it did exactly as I expected… nothing!
  3. Remove the “-” from any theme directories. I actually had one in there, so I removed it.
    This advice is a little silly too… hyphens are perfectly valid characters, but I’m getting to the point where I’ll try anything.
  4. Corrupt plug-ins are also to blame (apparently), but I don’t have any plug-ins yet since it hasn’t successfully installed at all.
  5. I’ve tried various other tips, but I tire of listing the stuff that doesn’t work!

Broken Theme Idea

The most useful site I reference was from BlueHost, and the broken theme idea got me thinking… have I jacked with these settings too much for them to have any hope of working?

I deleted the whole thing, and started over leaving out the themes I want to use for now. I wanted to remove that variable. I also removed the variable introduced Dreamweaver CS3, my editor. Like the instructions said, I used a straight up text editor to update the wp-config file. This last precaution is probably overkill, but I’m wanting to leave nothing to chance at this point! (Dreamweaver does update files when you change file names, after all.)

White Screen of Death. Grrrr…
added .htaccess back in (because that makes sense to me) … still nothing

Permissions

I’ve read and pondered a lot about permissions issues. So, I took to comparing the working installation vs. the broken one. I found two bits:

  1. The wp-content folder needs write permissions.
  2. The MySQL user permissions are USAGE (permission to connect and and perform basic commands only).

Regarding the MySQL user permissions:
WordPress recommends to GRANT ALL permissions. GoDaddy creates the database and it’s user with USAGE permissions. I was unsuccessful in changing that. Furthermore, GoDaddy GRANT access is set to NO.

Still Not Working

I won’t give up, though.