bahead
Forum Replies Created
-
Thanks for the response, that makes sense. I checked the protocol and you can’t include links to other folders in the same hierarchy either. So, unless one wants to create and maintain sitemaps for every folder, one needs have the sitemap in the root folder only, so it can include all subfolders. There are some websites where WP is installed in a subfolder, so I hope you can address this in the next release (because your plugin is excellent otherwise). For the time being, I’ll have to deactivate the plugin as to not negatively affect the current Google search/news indexing for my site.
Forum: Plugins
In reply to: [Rename wp-login.php] "You must log in to access the admin area."@markus That code doesn’t seem to work. I still get the default “You must log in to access the admin area”.
I was able to make the changes I needed to the WP Biographia plugin using the approach you suggested. Captions are now displaying with the avatars. Thanks again for your help!
Thanks for the quick response. I just realized that my issue is really with the WP Biographia plugin. I need to modify that plugin’s code to display the caption along with the avatar from your plugin. Your tips will help.
Forum: Plugins
In reply to: [Rename wp-login.php] "You must log in to access the admin area."Janneke,
This is an excellent plug-in, thanks! I’d also like to request the option to redirect the wp-admin folder to a 404 page. If the purpose of the plug-in is to obfuscate the use of WP on a site, then this option would help to do that.
Forum: Plugins
In reply to: [Raw HTML] HTML entities in [raw][/raw] tag if visual editor disabledI just upgraded to version 1.4.9, tested this again, and the problem still exists. After I disable the visual editor, edit a post/page with HTML code in [raw][/raw], and save, the code gets converted into HTML entities (which are then rendered as code on the page rather than interpreted as HTML). This also happens with any existing HTML in [raw][/raw] tags in the page/post.
No other impact other than that pages with file paths over 250 characters don’t get cached. I really just posted the comment so that anyone using the plug-in on a Windows server who can’t figure out why certain files aren’t being cached has an explanation.