Forum Replies Created

Viewing 15 replies - 16 through 30 (of 36 total)
  • Hi Marie,

    What is the reason you are unable to update to version 4.5.2? Is it not coming up as an update, or are you seeing errors when you try to update?

    And, just to rule it out, your site hasn’t automatically updated to 4.5.2 already has it?

    The main difference between the two is that PHPMyAdmin will make a backup of your data. So, all your posts, pages, settings, that sort of thing.

    With FTP you can make a backup of your site’s code. And most importantly, any custom code you may have in the form of themes, plugins, and wp-config.php settings.

    Ultimately, you will need both backups to restore a WordPress site.

    Forum: Fixing WordPress
    In reply to: site abroad

    Hey Enrique,

    This forum isn’t for that kind of accessibility issue. You will probably have better luck in the Troubleshooting forum here: https://wordpress.org/support/forum/how-to-and-troubleshooting

    However, I can tell you that I cannot load your site on that URL (I am in the US currently). But I can ping your server. I would consider looking at your host’s firewall, the configuration of any security plugins that may act like a firewall, or your server’s nginx/apache settings.

    That looks amazingly…normal. πŸ™‚

    At this stage, I would probably consider contacting your host to see what they can do to help out.

    One question though: Is your site meant to be accessed on ΓΈkobygg.no or okobygg.no? As a last-ditch effort, it may be worth a shot setting your siteurl to okobygg.no and see if that does anything.

    It does look like the theme is doing something weird there yeah.

    Without looking at the theme’s code I can’t say what it is you’d need to do to actually fix this though. But presumably it has to do with a custom portfolio post type. It may be hooking into save_post weird and producing some output too early.

    Contacting the developer would be the way to go, they should be able to resolve this for you. πŸ™‚

    It certainly does sound peculiar. Could you post the contents of your .htaccess file for me please?

    Hi there!

    Could you try hitting the “Save Changes” button on your permalinks settings page?

    If that doesn’t work, see if you can remove the .htaccess file (back it up first!) and then re-save the permalinks again to regenerate it.

    So this happens regardless of the theme you’re using? Did you try one of the default WordPress themes or without plugins?

    At this stage, it’s a bit hard to tell where the exact issue is, but there are a few things you can do to find out. First thing I would do is enable WP_Debug (http://codex.wordpress.org/Editing_wp-config.php#Debug) and try to reproduce the issue. This should give you at least an error message of some kind.

    That’s okay!

    So that error is related to the memory of the server your site runs on, and it looks like there’s something going on that’s causing it to run out of memory (which, currently, seems to be limited to 64 Megabytes – a little on the low side).

    Unfortunately, at this point it could be coming from anywhere and there are also several ways to solve this. You will want to refer to a developer to do an assessment of the plugins and the theme that are being used on the site to ensure that there are no memory leaks there.

    For the time being, would you be okay to find the wp-config.php file on the server (through FTP, or through your hosting provider’s file manager) and adding the following line near the top of the file (for example, just above where it says “/* MySQL settings */”)?

    define('WP_MEMORY_LIMIT', '128M');

    Alternatively, you could talk to your host about this and ask them to increase the memory limit on your site.

    Are there any plugins on the production site that don’t exist/aren’t active on the test site (or vice versa)?

    Since it seems that subpages work fine (like http://artisanofwhimsy.com/about/) and the links that are on there work fine (except for home, of course), I don’t think it’s related to the siteurl setting.

    Would it be possible for you to remove the .htaccess file (make a backup first) and let WordPress re-generate one (by hitting the “Save Changes” button on the Permalinks settings page of the WordPress admin)?

    Hi there!

    What is the exact message of the fatal error? It may give us a hint about where the error may be coming from.

    Also, have you tried disabling your plugins, and/or swapping to a different theme (preferably one of the TwentySomething themes!)?

    Which of the two installations are you using to reset the password with?

    From what it sounds like, the redirect may be messing with your reset password link and causing it to be “invalid”. What happens if you request a password reset from the domainname.com/wp page?

    Alternatively, do you have access to the databases for these installations at all (through PHPMyAdmin or otherwise)? This will probably be your best bet at circumventing the password reset loop and manually resetting the password yourself.

    The Codex describes how resetting your password through PHPMyAdmin would work, and also has a number of other ways to get a password reset: https://codex.wordpress.org/Resetting_Your_Password#Through_phpMyAdmin

    Do you have a copy of the site running locally, or can you get this set up to see if it happens there as well?

    My initial thought for what’s causing this is something the host has set up on the server and so setting the site up locally will help you confirm that.

    We’ve run into some issues before where the host was reverting the .htaccess file to the default every time it was changed (when we added redirects, for example). It’s possible that something similar is happening for this site with these files and so I’d consider contacting the hosting company.

    Hi there,

    It looks like a JavaScript error on the lookbook page is stopping from everything from “fading in”.

    I don’t know the theme or its settings, but the error seems to specifically occur in a bit of script that deals with the currency selector in the left sidebar (the one for the exchange rate widget).

    This is also why the other page works, since it doesn’t seem to contain the currency exchange widget and so won’t encounter the error.

Viewing 15 replies - 16 through 30 (of 36 total)