Forum Replies Created

Viewing 15 replies - 421 through 435 (of 1,808 total)
  • Hello, Chris, & welcome. Truthfully, in order to do what you wish to do, ie, have your permalink contain the word ‘blog’, you’ll need to have 2 separate WordPress installations, the 1 in your root folder & another in a subfolder under it called ‘blog’. You can easily export your current posts & then import them into the /blog installation, so you won’t lose any content. Then you can just not have a posts page on the root site, replacing it instead w/a link in your menu to your blog.

    The page name is not reflected in the permalinks structure. On my site, for example, my posts page is entitled “Vision Quest”, but the post urls will never contain that name.

    @hyrum0, just FYI, you’ll also need, once you’ve finished really cleaning up your site, to join Google Search Console:
    https://google.com/webmastertools
    & follow the instructions to verify your ownership of the site. From there, check your Search Console to see what Google is flagging, then request a site review. Check both the ‘Security Issues’ & the ‘Search Traffic’ tab of your console. Google does give indication that it sees (or at least saw) a site compromise, & you’ll need to get off their blacklist. Following these instructions will help you do that. Let us know if you have aditional questions.

    In addition, there may be other blacklists the site can be on, though I’m not seeing anything at the sites where I looked at this time. Hopefully Google is the only site flagging the recent hack.

    Again, let us know if we can provide further assistance.

    Hello, hyrum0, & welcome. When a site is hacked, you are no longer in full control of it. That may seem obvious, but it needs to be said in light of the following.

    In order to fix a compromised site, there are 2 objectives which need to be met. The first, &, to the site owner, the most obvious, is to repair the visible damage, which in your case was the defacement. The 2nd, which is actually more important, is to take away the control over the site that the bad actors now exert. You can eliminate bad files, but if the criminals still have control, ie, stolen passwords, etc, then simply eliminating bad code is not effective.

    The first thing you need to do is to notify your host. They may or may not help you, but, if this is a server-wide as opposed to a site hack, they’re really the only ones who can fix it.

    Next, ensure that whatever device you use to log into your website with is clean. If you have a keylogger or similar program on your device that sends your website’s credentials to the criminals’ command & control center, then no matter how good your credentials are, they’re compromised. So scan your device w/a reputable “virus” scanner, & preferably more than 1, as 1 might pick up something another doesn’t.

    Thirdly, make sure the network you’re using is clean. Don’t log into your website via an unsecured wireless network or public hotspot, as it’s possible your website’s credentials can be intercepted. If you upload files, use a secure method of file transfer such as secure FTP. If you haven’t changed the default password on your router, please do so now.

    Once you’re certain that your device & network are clean, change every password. That includes the one to your hosting provider’s control panel, your WordPress dashboard, & your WordPress database. Don’t forget to modify your wp-config.php file to reflect the change in password to your database. Make the passwords bulletproof. They should contain upper & lowercase letters, numbers, & punctuation signs. They should also not contain dictionary words.

    It’s also a good idea to change the ‘salts’ in the wp-config.php file by going to:
    https://api.ww.wp.xz.cn/secret-key/1.1/salt/
    Delete the ones that are currently in your wp-config.php & replace them w/the new 1’s that are generated for you. This will log all users out, including the bad actors, &, w/the change in passwords, should keep them out if the hack was caused by stolen/guessed passwords.

    Next, you should back up your site. If you don’t wish to back up the entire site, then at a minimum, back up your database, your user-generated files, ie, pics, documents, etc, & any purchased 3rd-party software like plugins or themes. You should also back up your wp-config.php & .htaccess files. Those should be examined to ensure that no bad code resides there. Feel free to paste these to any reply to this post, but *be ABSOLUTELY!! sure* to delete database credentials before doing so. You may also wish to use a plugin to export your content, such as posts, pages, & other custom post types on your site. That’s particularly applicable if there is no hacked content such as spammy links in your posts/pages. I often then import the content into the reinstalled site (see below) in order to use a brand new database & eliminate the possibility of using 1 that has been compromised.

    Before reinstalling the site, check your user files & any 3rd-party software for bad code. Sometimes bad code can be inserted into your user files, including images, so check these carefully. If you can redownload software you’ve purchased, use that instead of the files currently on your site.

    It’s a lot of work, but that should give you back full control & keep repeat hacks from occurring.

    Feel free to reply should you require further assistance.

    Hello again, penster4. It looks like you’re hosting w/one.com. It also appears they have a proprietary control panel, so I’m not able to be really helpful here, except to say that when you log into it, you should have an icon for your site’s file manager. Once you go into that file manager, you should be able to browse your files. They say the icon for their control panel is on the top right corner of their website.

    There may be an aplet called ‘errors’ or similar in that control panel that displays any errors your site may be throwing. Those could be helpful, if present.

    I wish I could be of more help, but, because this appears to be somewhat proprietary to one.com, it’s difficult, as I don’t have access, since I don’t have an account there.

    Well, 1 thing you could do is export any content using the wp-importer plugin. That way at least you won’t have to recreate all your content all over again, cuz that’s a royal pain.

    enyeartmarketing, you say you can’t log in. Does that mean that you can’t access a login page or that you can’t get past it? Because I am seeing a login screen when going to nettingwowrld.com/wp/wp-login.php. It’s pretty clear, though, that you’re running another plugin for login/registration purposes. Still, it might be a way for you to get into your dashboard?

    I’d also suggest that your permalinks are definitively impacted, ie, when I click the ‘About Us’ link, I get:
    “The requested URL /index.php was not found on this server.”

    That would suggest that, at a minimum, there is no .htaccess file in your /wp folder, & there needs to be if permalinks are to be saved. In addition, if you have WordPress installed in a subdirectory (like /wp), then you need to have a .htaccess file in your root folder as well as an index.php, the last line of which should look like:
    require(‘./wp/wp-blog-header.php’);
    if you want to have WordPress installed in /wp but you want to reach the site by typing nettingworld.com.

    you should be saving the wp-config.php file as ansi text just to be safe, as sometimes marks like the right single quote mark aren’t dealt with well, which might explain the x. I’ve actually never seen that before.

    Forum: Fixing WordPress
    In reply to: wp-admin

    Thanks for asking, cvmakato. Use your Godaddy file manager. Make sure the option to view hidden files is enabled. It will be in your web root folder, probably called public_html.

    Forum: Fixing WordPress
    In reply to: wp-admin

    Hello, cvmakato, & welcome. You appear to be getting a 500 internal server error. This can be caused by a variety of problems. Please paste your .htaccess file in your next reply, enclosing it in , ie,

    line 1
    line 2
    line 3

    .

    Let’s see where that gets us.

    Hello, thislittlepiggystayedhome. Use the ‘Recent Posts’ widget. You can put it in whichever sidebar you wish (assuming your theme supports it).

    Please let us know if that helps you.

    enyeartmarketing, those folders inside the wp folder, ie, wp-admin, etc, belong there.

    The site’s content, w/the exception of user files like pictures, documents, etc, is not stored in files, but rather in the database. Databases can be used if you reinstall WordPress, but you may have to do a search-&-replace on the urls to make them correct. You’ll also need to click the ‘Advanced Options’ in your hosting provider’s installation app in order to use the existing database, &/or modify the wp-config.php to reflect the appropriate database credentials. You’ll need also to ensure that your user files, ie, the wp-content/uploads folder & any other folders containing pictures, docs, etc, is saved to your local computer prior to reinstallation.

    If you’re feeling that all of this is just a bit more than you wish to cope with, you could submit a job to the WordPress job board on http://jobs.wordpress.net. This should not take long for someone w/experience to help you sort out.

    It appears that your WordPress install is currently located in a folder called wp. That folder, in turn, is in your root folder. I don’t know precisely what that’s called for a variety of reasons, the most notable of which is that hosting providers don’t have standards for those things. It could be public_html, htdocs, or any of a thousand other names. What I am saying is that it is possible to move the WordPress installation from the wp folder into the folder above it, ie, the web root folder. You will need to do a search_&-replace on the database & change the urls accordingly if you do that.

    Hi, matthisco, & welcome. Try putting a # in front of this line so that it looks like:
    #AllowOverride None
    & see if that doesn’t help. Please let us know, ok?

    Yeah, clearly something is amiss. Sorry for stating the incredibly obvious. W/o error messages to provide guidance, it’s hard to know precisely what that is. It can be anything from a plugin/theme conflict to a hosting issue or a combination thereof.

    After looking at this thread from the top, it appears this may have occurred following an update? If so, then 1 thing we might try is to reinstall WordPress. I usually do this using an FTP client like FileZilla, because trying to do it w/the hosting provider’s file manager can be pretty challenging.

    I instructed you in a previous post how to possibly obtain some error messages. Please consider following those to see if additional information can be provided & post anything you get to your next reply.

    You may also be reaching a point now where the technical help you require is beyond these forums ability to provide, ie, it necessitates someone logging into your site &/or control panel to figure out what might be occurring. You may wish to post a job to http://jobs.wordpress.net under either the ‘General’ or ‘Performance’ categories if that is the case.

    But let’s try reinstalling WordPress from scratch & also geting some error messages that may inform our next steps prior to taking that last action.

    I’m really sorry this is happening to you. To rule out a possible hosting issue, I would also be happy to provide a staging area on my server where we can test the site’s functionality. Clearly if it works there & not on yours, then you’re dealing w/a hosting issue. I’ve offered this to folks before, &, indeed, sometimes it has in fact been a problem w/the hosting.

    As I think you’re beginning to see, there’s a lot of parts that all need to function together to make a WordPress site work. When they do–& that is more often the case than not–they do so very well. When things break, trying to find out why can be a real challenge.

    I will be celebrating Easter w/my family later today, but I’ll respond as connectedness permits.

    Hi, penster4. Wel, I rather suspect that the best thing you could do is to pay for an upgrade. It could be that the theme is no longer in date, which, if I had to bet, is likely the cause of the difficulty you’re experiencing. Of course, if you paid for that & it wasn’t, you’d likely be pretty upset, & I guess I couldn’t blame you.

    On these forums, we can really only support the core themes, as it’s likely we don’t have access to themes others are using.

    Here are a few things that might guide your efforts, though.
    * Open your wp-config.php file & change wp_debug to ‘true’, log into your site, & see if any errors are displayed. This is a security risk, however, so please, for goodness sake, change it back when you’re finished! I can’t emphasize that enough.
    * Check your web folder & subfolders for files called err.log or error_log. If there are recent entries there, this may inform us as to where the problem lies.
    * Check to see if your hosting provider’s control panel has an aplet called ‘errors’. If so, & if there are recent entries, feel free to post them to your next reply. They may prove helpful.

    Hopefully something here will assist you in resolving this.

    It’s ok. You won’t learn if you don’t ask, & the only stupid question is the 1 you didn’t ask but wanted to.

    Just activate the Authentic theme (not the child) from your dashboard & try to customize it. If that works, then we know the child theme is at fault. If not, then please try switching temporarily to a default WordPress theme & repeat.

    There are *a lot* of things that can cause these sorts of problems–anything from a conflict between a WordPress theme or plugin to a hosting issue. The first step in the process is to narrow down the cause. Once we’ve done that, fixing things becomes a whole lot easier. I hope my thought process makes sense here. It’s very much like a doctor arriving at a diagnosis in order to be able to render treatment.

    You write really well, BTW.

Viewing 15 replies - 421 through 435 (of 1,808 total)