Forum Replies Created

Viewing 15 replies - 721 through 735 (of 1,494 total)
  • Bill

    (@chubbycrow)

    Make sure that line (1558) doesn’t have any spaces after the last letter of code.

    If you have a backup of that functions file, you can replace the bad one with the good one.

    Whenever you make changes like that, you should make them to a child theme so you don’t lose your changes when the theme gets updated.

    Bill

    (@chubbycrow)

    If you can’t access your admin pages, you’ll need to use an FTP client (like FileZilla), or your host’s cpanel (or File Manager) and navigate to the plugin on the server.

    In your WP installation there, find wp-content/plugins and delete that Google Analytics plugin folder. That will hopefully allow you to get back into WP admin.

    Bill

    (@chubbycrow)

    Are you still having a problem? Your site comes up fine for me, though a bit slow. The page is about 1.5MB, so that isn’t too unusual.

    Bill

    (@chubbycrow)

    When you say it crashes your site, what do you mean? What do you see?

    May we have a link to your site?

    Bill

    (@chubbycrow)

    When you tried your test comment, were you logged out at the time?

    Bill

    (@chubbycrow)

    Support for your theme is here:
    https://wordpress.org/support/theme/moesia#postform
    They’ll be the best acquainted with what you’re looking to do.

    Bill

    (@chubbycrow)

    Anything you write when creating or editing a page or post in WP is going to be inserted within the #content div. So yes, that ID will pertain to those specific elements of your site. (Other elements such as widgets will have different IDs, if any.)

    Again, best thing is to use the aforementioned web developer tools of your browser, inspect the element you’re interested in re-styling, and copy (or otherwise match) the existing selector string of that element in your new child-theme style rules.

    Bill

    (@chubbycrow)

    You’re welcome!

    Forum: Fixing WordPress
    In reply to: Remove a footer
    Bill

    (@chubbycrow)

    thematic_abovefooter() is an action hook found in the theme’s footer.php file. You may find a function inserting content into that action hook in the theme or child-theme functions file.

    EDIT: too slow once again 😉

    Forum: Fixing WordPress
    In reply to: Removing widget
    Bill

    (@chubbycrow)

    I am not seeing this in Firefox or Chrome. Have you tried clearing your browser cache and any caching plugin?

    Bill

    (@chubbycrow)

    Wish I could be of more help, but I think your best bet is to keep following up with the theme authors. There’s a lot of extra functionality built into that theme, and then with other plugins on top of that, it gets hard to untangle. Let us know how it goes, and good luck!

    Bill

    (@chubbycrow)

    ‘#whatever’ is just an ID added to a particular element by either WP core, the (parent) theme, a plugin, a function, or even created inline in a post. It’s source may well be WP in this case, but my point was that your child styles must meet the same level of specificity if they are to work. In this case, #content differentiates from #header, #footer, #branding, and so on. Make sense?
    #content .table3 td
    is more specific than
    .table3 td

    Bill

    (@chubbycrow)

    I get the feeling something may have happened to the wp-config file.

    There isn’t much in that file by default except your database connection info (unless you’ve added some stuff to it), so if your posts come up OK on the front end it’s probably OK. But you can easily compare it to the sample wp-config included in a fresh download and scan for anything unusual. (see: http://codex.wordpress.org/Editing_wp-config.php#Default_wp-config-sample.php )

    One thing to look at concerning those permissions quirks before doing a manual re-install: take a look at the permissions settings of your WP files and folders on your server. You can use an FTP client (like FileZilla), or your web-host’s cPanel or file manager to do this. (Or easiest: ask your web-host to check them for you.) Typically directories (folders) are set to 0755 and files are 0644. These are common settings for a shared-hosting environment, but check this page for your specific setup first.

    I would go ahead and take a site backup now anyway, even though it may contain errors. Database too. Chances are most of your files are fine. If your permissions look good, I still think re-installing WP is not a bad idea, just to get a clean start there. Just be careful about the files I mentioned in my prior post and be methodical and you should be fine. Let us know what you learn.

    Bill

    (@chubbycrow)

    You can try doing an auto-reinstall from the Dashboard > Updates admin page for starters, and see if that helps.

    Before you do any further updating beyond that, make sure you have backups of your site files and your database as well. All of your posts, pages, and settings are stored in the database, so they shouldn’t be affected by replacing WP files and directories. Your images though are in the wp-content directory along with themes and plugins.

    With that in mind, for a manual installation you can download a fresh version of WP and unpack it. On your server, delete and replace all WP files and folders with new copies except for:

    do not touch wp-config.php (it has your database settings)
    do not touch the wp-content directory (for reasons stated above)

    Bill

    (@chubbycrow)

    I can’t be sure, but I’m guessing that you may be using WP eCommerce for your inventory display and sales? If so, try asking about this on that plugin’s support forum for best results.

Viewing 15 replies - 721 through 735 (of 1,494 total)