ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Login Redirect Extension Doesn't Work

March 08, 2012 1:41pm

Subscribe [2]
  • #1 / Mar 08, 2012 1:41pm

    BVUUF_MSC

    22 posts

    Sorry if this is the wrong forum. I thought that Development & Programming would also work but to be honest I don’t understand any of the thread titles there.

    This was originally posted here. I’m sorry also if that was the wrong place but as you’ll see this has been a problem for a LONG time and I’m fed up, frustrated, and pissed that there are no ways to make our website accessible for the people who use it most.

    Hello all,

    I’ve been having a huge problem getting the Login Redirect to work. It’s imperative that we get it or something like it to work because our church website is accessed by a lot of people who are elderly and/or don’t have a lot of computer experience. We get emails and calls every day in our office about login problems.

    So anyway, I’m using the EE1 version of this on EE1.7.1.

    I installed it so that our users wouldn’t be sent back to our index page. However, now upon logging in or out, they get a bad link to the effect of sitename.orgindex/template_group. I am wondering how to add the / back in between the .org and index. Because of this I’ve had to uninstall it, but the same problem keeps happening of people ending up on pages they didn’t want to end up on when they log in.

    Thank you for helping me to fix this, fixing it, or referring me to another extension that works.

    EDIT: I already posted this at Devot-ee back in January, but again, I already got three requests this morning (2/19) to show people how to log in (since without this plugin folks are sent back to the homepage), so we need something like this extension, if not this extension, to function so that people don’t have to keep emailing us and calling us just to get into the website.

    I opened up the file in Notepad and I saw a line that says, “//Remove last slash from url and set base” Is that what is causing the problem? Is it as easy as deleting this? I just need that slash added back in. That is all, and then it’s fixed.

    Thank you.

    Again, this is something we’ve had to deal with every day for a couple of months because nothing else works. I can’t even change the menus to link directly to a PDF. I’m frustrated and pissed off with EE and this close to trying to find another solution, but everything else is either too complicated like EE or it doesn’t meet our needs. All we want is a basic, static website, a newsletter, and a member-only area. Is that so hard to do?

    I’m sorry if I sound stand-offish but I’m just seriously at the end of my rope and our congregants and staff are getting there too. I know there are problems in general with our build but I don’t have a darn clue how to fix any of it, and if even this one small thing can’t get fixed then I don’t know what to do.

    Thanks for any help at all.

  • #2 / Mar 08, 2012 6:09pm

    John St-Amand

    865 posts

    Sorry to hear you’re having a hard time, Kyle.  Generally, “a basic, static website, a newsletter, and a member-only area” is not overly complicated to handle in EE, though there are numerous ways to accomplish each, particularly the member-only area.

    I’ve not used the login redirect plugin but it seems like that’s contributing, at least in part, to your URL issue, whether through a slash missing in the pluging’s settings, through htaccess or through your general configuration settings in EE.

    The one and only screen cap of the add-on on devot-ee is EE2, so I can’t say whether the settings would all be the same or all be labeled the same way, but there are certainly a few lines in there that may add the slash, but you might also look at your general setup first.

    Are you using htaccess to remove index.php?

    If you look at admin > system preferences > general configuration - what do you have in “Name of your site’s index page” and “URL to the root directory of your site”?  If, for example, the latter does not include a “/” you could add it - because it’s default, normally, is to include one - which may be what the plugin is referencing in its targeting of the trailing slash.  I’ve not a plugin dev, so I’m just throwing out an idea for you to explore.

    The other thing you might consider, though I realize at this stage and given your frustration you might not consider it, but there is more than one plugin available for EE2 that provides this same functionality, and so you might have more alternatives available to you if you were to consider an upgrade - but again, i understand you’re looking to get the investment in time you’ve already made working first and foremost.

  • #3 / Mar 09, 2012 11:30am

    BVUUF_MSC

    22 posts

    Does upgrading to EE2 change anything major? Or is it like Wordpress where it upgrades and nothing has changed? We have a disc that has EE2 on it but I have no clue how I would salvage our old website if anything goes wrong since I can’t even figure out how to back up our current website. For all the web stuff I’ve done in the past I’m pretty clueless when it comes to PHP and all the other stuff it requires in order to work.

    We don’t have a slash in our root directory—I’ll play with that and see if it helps. Thanks!

  • #4 / Mar 09, 2012 11:36am

    John St-Amand

    865 posts

    Generally, the fewer add-ons you are using in your site, the easier the upgrade path is with EE2. That being said, when you do an upgrade of any kind, it’s always recommended to backup the database and the site files to be safe.  I wouldn’t suggest doing an update without taking that precaution.  The database backup is generally accomplished through your hosts’s MyPHPAdmin panel - you can ask them about it easily enough, I would think.  The upgrade instructions available in the user guide on expression engine.com walk you through the process of updating step by step.  I’ve done a couple of updates and they’ve gone fairly smoothly.  Certainly if the add-ons you’re using for EE1 have a version for EE2, you shouldn’t have too much difficulty updating them as well, which makes the process a little easier.  There’s certainly some features of EE2 that are worthwhile - snippets being the big one.

    Hopefully the slash in your setting does the trick on that front.  The upgrade was just another of the “nice to have” things that you could choose to tackle down the line to take advantage of some of the newer features.

    All the best, and hopefully your experience with EE keeps getting better from here.  It’s a terrific system with a great community.

  • #5 / Mar 16, 2012 7:17pm

    BVUUF_MSC

    22 posts

    Adding the slash fixed it!! Thank you so much!

  • #6 / Mar 16, 2012 7:37pm

    John St-Amand

    865 posts

    Whew. Glad to hear it.  If you have any other questions for the EE community, post them to the community forum, or post to Twitter with #eecms.  Great bunch and we’re always happy to try to help.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases