Forum Replies Created

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter bcrider

    (@bcrider)

    Still seeking help with the issue.

    Thread Starter bcrider

    (@bcrider)

    Thank you James πŸ™‚

    Thread Starter bcrider

    (@bcrider)

    Hi James,

    Yes, Multi-site install.

    I see the section that talks about Multi-Site in the support article you shared but it seems to reference moving to a new server or changing domains.

    All I need to do is change the directory and I don’t see any reference to that? Is there another article I should be referencing?

    Thanks!

    Thread Starter bcrider

    (@bcrider)

    Hello,

    In step 3-5 of the support documentation for moving directories on your existing sever:
    https://codex.wordpress.org/Moving_WordPress#Moving_Directories_On_Your_Existing_Server

    It states to:

    3. Go to the Administration > Settings > General panel.
    4. In the box for WordPress Address (URL): change the address to the new location of your main WordPress core files.
    5. In the box for Site Address (URL): change the address to the new location, which should match the WordPress (your public site) address.

    When I go to the Administration > Settings > General panel I do not see anything that references WordPress Address (URL): or Site Address (URL): and therefor I cannot complete these first steps?

    Am I doing something wrong?

    Thread Starter bcrider

    (@bcrider)

    Did you undo that change in wp-config.php

    Hi James,

    Thanks again for your support on this!

    Yes, immediately after making the 5 character change to the config file and realizing it broke the site I edited the file back to it’s original state. Upon doing so, I still got the two error messages I listed above.

    When accessing http://www.pismocoastsurfcamp.com/wp I get the permission error:
    Forbidden
    You don’t have permission to access /wp/ on this server.

    And when I access the wp-admin:
    Parse error: syntax error, unexpected T_STRING in /home/pismocoa/public_html/wp/wp-config.php on line 79

    Should I focus on the first message and consult my host to see if the permissions need to be updated?

    Should I create a brand new config file and and manually enter my specific credentials (since I didn’t make a back up, banging head on computer)?

    Thank you!

    Thread Starter bcrider

    (@bcrider)

    Hi James,

    Thank you for the support article! It sounds like that’s the one I should have used…(I used a different set of instructions I found on the support forum) and unfortunately now that I broke the site…I can’t use the correct one you linked. πŸ™

    It appears I need to fix what I broke before I can follow the correct directions?

    In hindsight I should have also made a copy of the wp-config.php prior to changing it. In my defense my logic was that I was literally just removing five characters ‘/wp’ and if it didn’t work I could just add them back. Lesson learned the hard way…

    So here’s were I’m at:

    1. I’m 99% sure its a multi-site, not a single instal but how can I tell?

    2. The only changes I made were to the wp-config.php file on line 78.

    I changed the path from:
    define(‘PATH_CURRENT_SITE’,’/wp/’);
    To:
    define(‘PATH_CURRENT_SITE’,’/’);

    I was then going to move the wordpress files out of a folder called WP to the root directory. Upon doing so it broke the site. I tried to put the files back into the WP directory and add the /wp back to the config file to no avail.

    3. Now when I go to the original URL http://www.pismocoastsurfcamp.com/wp I am greeted with the following error:

    Forbidden
    You don’t have permission to access /wp/ on this server.
    Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request

    If I try to go to the admin panel at http://pismocoastsurfcamp.com/wp/wp-admin/ I’m greeted with this error:

    Parse error: syntax error, unexpected T_STRING in /home/pismocoa/public_html/wp/wp-config.php on line 79

    Looking at line 79 in the config file its the line below the one I tried to edit. I read that the error could be a hidden character like a space or something but I can’t find one.

    So…..given all that info. Do you or does anyone have any idea of what I need to do to get the site back up so I can follow the correct article you posted? The first error message that speaks to not having proper permissions….is that something I should focus on?

    I really need help and would be very grateful for some. Thanks. πŸ™‚

    Thread Starter bcrider

    (@bcrider)

    Disabling all plugins one at a time and testing worked!

    Then a re-enabled them all and it still works.

    THANK YOU VERY MUCH!

    Thread Starter bcrider

    (@bcrider)

    Akismet is the security plugin. Can you recommend another as well?

    I will try disabling the plugins now

    Thread Starter bcrider

    (@bcrider)

    Login with Ajax is what I was using but I removed the plugin and tried using the standard wp login widget. When attempting to login, it accepts the username and password but just takes you back to the homepage (not logged in).

    I’m stumped and really need some help

    Thread Starter bcrider

    (@bcrider)

    Third time begging for help is a charm?

    Thread Starter bcrider

    (@bcrider)

    Hello,

    I’m still seeking help on this issue. All users and admins are still unable to login on the front end.

    Please help.

    Hello

    I’m trying to accomplish this same task if someone could be provide some assistance.

    When the visitor clicks on the Login With Ajax register link, I need to point them to a different register page. Is this possible?

    Or, as a side question. If I do not point to another page, is there a way to add more security such as manual approval to the registration process? As it stands now, a new visitor can register with just a name and email. This seems like a recipe for spam accts?

    my example is here: http://splitboard.com

    Thanks!

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