ks4el
Forum Replies Created
-
Forum: Plugins
In reply to: [Dynamic User Directory] Reading wrong prefix wp_ vs wp_3_Hi Sarah,
Thought this made it via email but it didn’t go anywhere, sorry about that.
Thanks for getting back. I have found that the different prefixes are indeed related to the different sub-domain sites. Looks like the overall network items and the first site I configured are wp_ and the subdomain only items are wp_3_
So it depends on how I activated the plugin as to which prefix gets used. I don’t know enough of the internals to know if that’s normal or not but it’s what I ended up with just by following normal set up instructions from the WordPress.org docs.
Please let me know if there is anything I can do to help debug on my end. Happy to help.
Thanks,
SteveForum: Plugins
In reply to: [Dynamic User Directory] Reading wrong prefix wp_ vs wp_3_One other thing, as expected, when I did that it now gives me all users regardless of whether they are a user on that particular site or not. It would certainly be best if it just gave users for the given site. Yes, users can be manually removed, but that doesn’t work well for multiple sites with lots of users.
Thanks again!
Forum: Plugins
In reply to: [Dynamic User Directory] Reading wrong prefix wp_ vs wp_3_Looks like my hack didn’t affect the CIMY fields after all. Hopefully all this is helpful for a fix.
Thanks!
Forum: Plugins
In reply to: [Dynamic User Directory] Reading wrong prefix wp_ vs wp_3_Here is a bit of an update on my part. While no php developer, I am well versed in several other languages, so I tried a little hack. I went through and replaced the prefix variable with “wp_” everywhere and now I see the users, so my guess must’ve been correct. The problem though is to use CIMY user extra fields with DUD it’ll be confused since they are in 2 different prefixes. Users in wp_ and CIMY in wp_3_.
I hope this helps. I’m surprised I’m the first one to find this, maybe I did something odd in the setup that triggered it.
Thanks!
On second thought, maybe I just switch to LDAP. It looks like WP, gallery, and apache will all work with LDAP. I think that’s all I need.
Andrea and David, thanks for your replies.
I’m using Mac Mail which from what I can tell does allow username and password to be asked for. The Restricted Site Access plugin generates a page for the */feed/ but it is a login page so the feed reader doesn’t recognize the format since it’s just a web page.
I tried Feed Key which appears to require Members Only plugin to work. That, while it had a few things that were a little clumsy did indeed work. The only problem was that it was an all or nothing for the entire site and had no ability to have the top level open and only certain subdirectories restricted.
I’ll try the plugin David recommended next and see what happens.
I had another thought after getting a little sleep last night. Perhaps I can just use htaccess approach, but I don’t want the users to have to have one more password. So the trick there will be if I can find a way to get the normal user level approach to work with that.
Thanks again!
Forum: Networking WordPress
In reply to: Site path has dbname in it, can't get rid of it!Andrea, thank you very much! I’m gonna chalk that one up to way too little sleep. I didn’t use dreamhost, but that told me what to look for. I used debian’s apt to install the initial package and a script that comes with it to create the initial configs. I then updated to 3.0.1 manually. I then followed the directions too literally and put the lines from the network tool in the wrong file which left, as you mentioned, $base = dbname. Every time I’d look I was then looking in the correct file. When I did a grep that showed me where the problem was.
Thank you, thank you, thank you!
Forum: Networking WordPress
In reply to: Site path has dbname in it, can't get rid of it!Oh, if it wasn’t obvious, it’s subdirectory not subdomain.