Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Did anyone else report something like this? Our editors have been a part of our “WordPress” AD Group for several years and this has been working fine. But perhaps with a recent upgrade, users are not able to authenticate. I turned off the Authentication Group option and a user account authenticated, which had been failing.

    We are in the process of switching from ADI to NextADI and are having the same type of problem. I noticed that you are trying to use STARTTLS on Port 636. In the configuration area for this, it states that you need to use Port 389 for STARTTLS.

    Not sure, but I think the focus should be on the cause of the error, “[ERROR] Authentication for user ‘cwolff’ failed because: Can’t contact LDAP server” I’m going to read more on STARTTLS and how that affects communication with the LDAP server (if it does).

    Thread Starter bgibson135

    (@bgibson135)

    I’m not sure that I’ve found the cause of this problem, but I compared this user’s account with others and noted that it had been created without the additional “@xxxx.xxx” info. There was a field in our AD system that didn’t have the correct info. I am thinking this was the cause of the problem. Thanks.

    We lost our settings with 1.1.7

    I did not do the original install of ADI, but we have a multisite WP instance and ADI is working fine on it. We have experienced the issue described, where an authenticated user for one site doesn’t have Dashboard access to another site. We had to add that user to both sites with a role that has Dashboard access. *Our users are added with “Subscriber” access to the root site, and then “Administrator” access to their individual sites.

    I normally am authenticated as Super Admin, and did not realize that Administrators see the ADI interface on each of their sites. It freaked me because I thought that if they made a change on their site, it would change everyone else’s… but it doesn’t. Still for our type of users, I would prefer to only allow a Super Admin to access the ADI interface, and everyone else to not even see it.

    I wasn’t suggesting “we” do the rogue offshoot.

    I had installed the plugin, and yes, it makes the Advanced Image editor menu look like it should, without a plugin.

    Links: By categorizing links, I could create multiple dropdown windows which had only links for a specific topic.

    Image border, padding, and while you’re at it Links;-) When you have to start relying on a 3rd party to keep their plugins up to date, just so you can have basic functionality (that had been around for years) then you start questioning how far out on the limb you want to go. But, WP is open source right? You could have someone start developing a “User Friendly” fork and the rest could go with the “Developer Version”.

    ??”…pretty quiet and uneventful from a support perspective”?? Well, of course… the more functionality you drop out and push off onto a 3rd party plugin, the less that will be expected of you.

    Oh, yeah! Removing a way to easily add an image border, and padding around an image, is a new WP “feature”. I catch that there is a right, and wrong (different) way of doing these things. I also catch that all the users (students/staff at college) that I want to give a useful communications tool to, that they don’t have to learn CSS or HTML to do some simple functionality, isn’t a step forward, but backward.

    You can explain it all you want, but if a majority of users go, “Huh” then what have you gained? Less users.

    The easy way to accomplish this is to use the RSS import feature with your import file having the following for each post (item):

    <ITEM>
    <PubDate></PubDate>
    <Title></Title>
    <Description></Description>
    <Category></Category>
    </ITEM>

    The “category” entry needs to be spelled exactly as the existing category in WP.

    You don’t even have to include the standard feed file headers & footers.

    I recently imported a file with about 600 posts in about a minute.

    This is a nice change in menu naviagation. Alleviates the need to scroll down to get to menus at the bottom of the page, or clicking an area to see sub-menus.

    Thanks!

    Forum: Plugins
    In reply to: WordPress Mobile Edition

    “WP Mobile is incorrectly installed. Please check the README.”

    The problem for me was that this plugin zip file actually had a file that goes in the plugins folder ( “wp-mobile.php” ) AND a theme folder ( “carrington-mobile-1.0.2” ). Unzipping the file created a ( “wordpress-mobile-edition” ) folder with the theme folder beneath it, and the “wp-mobile.php” file in it.

    To add to the confusion, I had already installed a “carrington-mobile” theme previously, so wasn’t thinking that I had to do anything but place the original unzipped folder in the plugins folder.

    *Now that I think about it, I used the Plugins Installer and apparently it did not put the files in the correct locations.

Viewing 11 replies - 1 through 11 (of 11 total)