camner

Does that mean that there is no way to display a route in a post or page in your free version?

Thank you for your reply. I have looked at the resources you suggested. I have also watched a number of your helpful videos about the plugin.

I AM able to add routes successfully.

What I canNOT do is to have viewers of the blog see the routes on blog posts or pages.

How does one “embed” a route on a post or page? Other map plugins use shortcodes for this. Your PRO version has a shortcodes tab, but your free version does not.

Is there no way to have a blog viewer see a CM Map Routes Manager (free version) route on a blog post or page?

Thank you again for your help.

You are far more expert than I with WordPress, but I’m a bit confused by your statement that “WordPress didn’t create the blogs.dir folder.” The install folder (called “WordPress” that I downloaded from the WP site does NOT have a “blogs.dir” folder in the wp-content folder. After uploading the WP files to my server and running the install procedure, the blogs.dir folder appeared. So, wasn’t it WP that created the folders during the install process? I know I did not create them myself!

I am going to ask my webhost to enable SSH access for my account, which will allow me to examine and change folder ownership. From Googling around, it seems that I have the potential to break WP in the process! Any words of advice on how the ownership of blogs.dir and the subfolders should be configured to allow FTP access into those folders?

Thanks for your replies. I’m NOT asking about FTP permissions…the issue is ownership. It doesn’t matter what the permissions are set to (even 777!), the folders aren’t accessible via FTP client because the ownership prohibits it.

As for backup, I can certainly back up on the server to the same server, but that doesn’t help in case of a server loss or corruption. I’d like to move these files “off host” from time to time, just in case.

Aha….Andrea_r gave me the answer just after I figured it out on my own, it seems! Thank you!

OK….I figured out my own problem. The $base variable should have been set to ‘/blogs/’ not to ‘/’, and I don’t need the ‘PATH_CURRENT_SITE’ variable to be set (i just commented out that line.

That (seems to) fix the problem.

Also, by doing some additional reading, it’s the .htaccess file (which I’m not savvy enough to understand exactly how the rewrite rules are working) that does the magic in terms of making the web server think it’s going to a subdirectory which in fact does not exist.

I think the difference is that bloginfo prints directly to the web page, and get_option returns a value. That’s why to output a value using get_option one needs to use the php echo(); function.

After more poking around, I discovered that the registration emails that were not going through (at least the ones I could test) were failing due to a “550 Callout verification error”. I contacted tech support for my webhost (where my email is hosted) and they turned off “callout verification” (whatever that is), and that solved the problem.

I’m still concerned that WP has changed somehow the method of sending emails, because going back and forth between a WP 2.2 and WP 2.3.1 installation reproduces the problem each time.

There is a beta version of a plugin here that will do this (it’s called Bouncer). The only weakness I see is that it does not inform users that they must be approved. So, WP still says “check your email” and the email won’t be sent until the registration is approved.