Forum Replies Created

Viewing 15 replies - 1 through 15 (of 22 total)
  • Thread Starter BobTheClock

    (@bobtheclock)

    I installed the WPFront User Role Editor plugin and it has given me some pretty slick control over roles.

    Thread Starter BobTheClock

    (@bobtheclock)

    Well, a lot I don’t know. I guess I can’t give them 1 Author account to share or even 1 account each since the Author role only allows the management of Posts, not Pages. Weird. Why is that?

    My website does not use Posts, just Pages.

    Is there another way I can grant an author-like role to more than one person so that they can only author their pages, but not others’ pages?

    I’d rather not give them the Editor role as that allows access to every page.

    Thank you…

    Thread Starter BobTheClock

    (@bobtheclock)

    Thanks anyway!

    Thread Starter BobTheClock

    (@bobtheclock)

    By the way, I’ve created several subdomains that all behave as described above. The redirect to the public_html/subdomain folders work, but how do I go about keeping the subdomain in a visitor’s browser address bar rather than the folder path?

    Many thanks…

    Thread Starter BobTheClock

    (@bobtheclock)

    Jame’s – a bit more information, if you’re interested:

    Rick,

    When there is a bad AddHandler directive in your .htaccess file, you can fix it by commenting it out with a # in front, or just deleting the line. The directive looks like this:
    addhandler application/x-httpd-php52

    You can edit your .htaccess file using the File Manager in cPanel, if “show hidden files” is enabled, by looking in the folder where your site files are kept.

    Sincerely,

    Josh D
    Jr. Technical Operations Officer
    Arvixe

    Thread Starter BobTheClock

    (@bobtheclock)

    Whatever they did, it’s fixed now. I sent a reply asking to know more, what I might have been able to do to fix it myself…

    James, I learned a small/big amount. Thank you. Your explicit ‘splainin’ skills are not write-home-about-it-able, but if one looks in deep enough to see, you say what you mean.

    Thanks again,

    Rick

    Hello Rick,
    This has been corrected for the domain carkeekpark.org now. Most probably this issue was due to php handler. Can you please check this now and let us know if the issue is still persist.

    Simon M
    Technical Support Officer Ninja

    Thread Starter BobTheClock

    (@bobtheclock)

    Got it!

    Thread Starter BobTheClock

    (@bobtheclock)

    I will do that, James. But just to be clear…

    I don’t know if this matters, but none of these are reported as “404 errors” as I have seen in completely unrelated web browsing experiences in the past.

    What I get (eg, Dashboard > Plugins) is a rendered page as if I had selected “Visit Site” from the Dashboard with side widgets, header, background all in tact but the central or main blog area where pages load is blank with Not Found in bold with It looks like nothing was found at this location. Maybe try a search? on the line beneath.

    Perhaps that is referred to as a 404 error, but I never used that reference, just that it was a Not Found page. Dang, I hope that isn’t a crucial distinction.

    Thread Starter BobTheClock

    (@bobtheclock)

    Another detail:

    If I select/click Dashboard > Appearance or Dashboard > Plugins, I get the Not Found page.

    If I hover over Dashboard > Appearance, the sub-menu appears and I can successfully select all items except Themes (gives Not Found).

    Similarly, I can hover over Dashboard > Plugins and select Editor successfully, but both Installed Plugins and Add New give the Not Found page.

    I see that there are at lease a couple of versions of plugins.php and themes.php in /wp-admin/ and /wp-admin/includes/ respectively. What are the issues with replacing these? And with what?

    Thread Starter BobTheClock

    (@bobtheclock)

    I looked at permissions on themes.php and plugins.php and they match widgets.php in /wp-admin/ and widgets open normally from the Dashboard.

    I renamed /plugins/ and created a new /plugins/ folder with just the generic index.php and hello.php in it. Same result after logging into the Dashboard again – Not Found pages.

    Thread Starter BobTheClock

    (@bobtheclock)

    Wow, I went ahead and did (1) and (2) above. Whew. Renamed twentyfourteen and copied a fresh download from WordPress to the /Themes/ folder.

    However, that did not work either. Dashboard Plugins and Appearence > Themes both give Not Found pages precisely as before. And before that.

    The amazing thing to me is how simply these things can be tested by replacing entire folder structures.

    As I mentioned, themes.php and plugins-php are there. Is the next step to replace some aspect of the /plugins/ folder? I don’t think that would disrupt much since the ibs-calendar plugin hasn’t been populated with any content or even synched yet with any calendars. limit-login-attempts and social-media-plus will be easy to re-install as well.

    Anything noteworthy or different about following a similar procedure as we did with Themes and WP itself?

    Thread Starter BobTheClock

    (@bobtheclock)

    Sorry, just content editing — I’m not hacking .php files yet.

    James, am I (1) renaming the existing twentyfourteen folder and then (2) creating a new twentyfourteen folder with the new theme files/folders without some sort of executable installation? It’s as simple as what we did with WP itself?

    Thread Starter BobTheClock

    (@bobtheclock)

    Thanks James.

    themes.php and plugins-php are there. Seems every file in /wp-admin/ have exactly the same updated time/date attributes from last night at 11:21 PM. That’s normal right? I just did a bit of text updating variously.

    I’ve never even opened .htaccess before, though it gets talked about alot. An opportunity to learn!

    AddHandler application/x-httpd-php52 .php .php5 .php4 .php3

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

    When I called my Arvixe host tech support as mentioned before, the fellow and his supervisor seemed just glad that a WordPress person (“you”) told me what to tell them, which they re-worded and told me back again. I think I’ll need to help them help me, if you know what I mean – which I don’t mind. Any tips on inspiring them to helpfulness?

    If I upload a new 2014 Theme, any tips on ensuring my content is still there and preserving modest widget customization?

    Thanks James,
    ~Rick

    Thread Starter BobTheClock

    (@bobtheclock)

    Well. The Earth is indeed still spinning. (2) above should read “upload WP Zip file to a folder on server and use Extract to extract files” because cPanel File Manager only lets you upload one file at a time. Or, as you suggested James, use FTP. The entire process only takes a few minutes.

    That said, it did not work.

    I removed the 16 WP root files and 2 WP folder except wp-config.php (file) and /wp-content/ (folder). Then I copied those same files from the fresh WP download to their proper locations.

    I then went to the WP Dashboard, was told the database needed to be updated, and then I logged in. Dashboard plugins and Themes return a Not Found page precisely as before.

    Since I can’t get to Themes, is there a way I can download 2014 and remove/replace it in a way that is similar to what I was just taught for WP without affecting the content? Other ideas perhaps?

    I learned quite a few things James. I’m not disappointed.

    Thanks,
    ~Rick

    Thread Starter BobTheClock

    (@bobtheclock)

    No that’s not right. It should be:

    (1) download the compressed WP file from the Download WordPress link above to local PC
    (2) extract compressed files into a folder on local PC
    (3) except for wp-config.php (file) and /wp-content/ (folder), delete all like-files/folders from server installation of WP rather than overwrite the files with new ones; this is because we need to be certain the originals are replaced completely
    (4) upload new like-files/folders to server location

    From my freshly extracted local WP folder, I see that there will be 16 files in the WP root (/public_html/ on my host server) and 2 folders, /wp-admin/ and /wp-includes/ to delete on the server and replace with new copies.

    That will leave the original wp-config.php (file) in the WP root (/public_html/ on my host server) and /wp-content/ (folder).

    Is that closer to about right? I still haven’t done this.

    ~Rick

Viewing 15 replies - 1 through 15 (of 22 total)