gdelisle
Forum Replies Created
-
Forum: Plugins
In reply to: [Captcha] BWS Menu breaking my adminHi, thanks for your reply. I have already found the problem. As I explained, this is not a PHP error but an incorrect path, which results in 404 errors in the web server. This probably results from the way you are creating $bws_menu_current_dir which does not respect the WP constants like WP_CONTENT_DIR, WP_CONTENT_URL, WP_PLUGIN_DIR and so on. In installations like mine where these constants are set in wp-config.php, they tell WP exactly where to look for the plugins directory instead of assuming the path is the same as the directory on the machine. As a result your variable is looking for a directory on my web server that doesn’t exist. Since you load scripts, styles, and images via this incorrect path, your BWS menu area is broken and the javascript errors are somehow compromising other areas of the admin. A rollback to Captcha 4.2.6 and Contact Form 4.0.3 returns the menu to working order. Please pass this on to your developers and scold them to respect WP internals, this is exactly why they are there!
I already submitted a request via your help center but I received no response there.
Forum: Fixing WordPress
In reply to: Password not recognizedThanks NeoTechnomad for this link which helped me with this problem. I tried many solutions before this which did not work — I used the reset function many times, disabled all plugins, reset several times through phpMyAdmin, tried the emergency script, replaced the user with a known good copy from another database, and each time the process appeared to work, but the password was always rejected.
At this point I suspect some corruption of the wp-users and/or wp-usermeta table is involved. Nothing whatsoever can be done with the old admin user to make it function, but the new admin user is working fine.Forum: Networking WordPress
In reply to: Multisite planning troubleNot quite. The WP install “lives” at the IP address that’s mapped to ornithopolis.org, but the site that it serves is underneath http://www.birds.cornell.edu, so the root of the network is at http://www.birds.cornell.edu, and traffic gets to/from it via a proxy rule in IIS. So I can set up /blog and it will appear at ornithopolis.org/blog, and with a rule to proxy ^/blog(.*) it will also appear at http://www.birds.cornell.edu/blog and work beautifully.
The problem occurs when I want to map a new domain, in this case yardmap.org, to that blog. If I set up the cname to point to http://www.birds.cornell.edu, it’ll go to the IIS main server instead of WP and the main server won’t have the mapping. If I point the cname to ornithopolis.org, WP returns a 404.