Forum Replies Created

Viewing 15 replies - 91 through 105 (of 681 total)
  • Have you considered pressing Ctrl+F5?

    Now, getting back to business. Try to stay away from caching or optimizing plugins, at least until you are happy with the contents of your website. First build it, than optimize.

    Also, for best results you should crop the featured images for the pages used in featured pages block to 270 x 250px, or bigger, but within these proportions (square images ~ more or less).

    Other than that, try not to over-complicate things. And don’t be paranoid about your website’s security. WP is secure, as long as your username is not admin and doesn’t have a very simple password. And always think twice and look at the plugin rating and comments before installing one: plugins are the main backdoor for the real threats to your wordpress security.

    Not brute force.

    Before you start reactivating any of the plugins we should have the theme looking and working properly, don’t you agree?

    Please disable ALL plugins and leave them disabled for now. And, of course, reupload Customizr in its folder. Make sure all files are there. Right now they are missing.

    Well, 10 mins ago the scripts where there. Now indeed I get the (not found) for all of them (which is good, because when we started they were missing with no error being triggered).

    Might have to do with some weird stuff going on in .httaccess and maybe forbidding access to your theme files?
    This is how it should look like:

    # 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

    You should find .httaccess it in root. If you don’t have it, create it with the contents above.

    At this moment scripts are loaded. I do not understand why the CSS is not. Anyway, I told you above how to quickly disable all plugins. Append an underscore to the plugins folder and load Dashboard->Plugins once. WP will instantly disable all your plugins. After that, rename your plugins folder back, by removing the underscore and reload the Dashboard->Plugins page once more.

    Now all your plugins are disabled and your homepage should be ok (if your problem had to do with some plugin).

    On a different note, what files are in your child theme? And, more specifically, is your child theme’s functions.php empty, with just a

    <?php

    on line 1? That’s how it should be when you start a child theme.

    Yep, I did run __after_loop twice, once for posts pagination and the other one was the default, for the static page comments. If you look in theme functions, singular __after_loop contains comments, while lists __after_loop contains pagination (archives, blog, author, meta, tag, search, year, day, week, etc…) .

    I didn’t need or want the static homepage __after_loop, but the probability of a homepage having comments activated and actually having comments was so small that it didn’t matter at the time. Normally, that specific page should have comments disabled, even if comments on pages were allowed by theme. And best way to do it would have been programatically. Way out of scope at that moment.

    Yes, customizr’s bootstrap.min.js is in the right place. And WP only loads theme files from two folders: customizr-child (the active theme) and customizr (the parent theme). All other themes are ignored. Go through the steps I described above and let’s see if it’s a plugin or the child theme first.

    You still do not load core javascript files from parent theme. If you say it’s complete (as in ALL the files are there), it’s clearly not loading. This might have to do with:
    1. Corrupt files in child theme that are loaded instead of parent files (in order to check this you could upload an archive of the contents of your child theme somewhere and let me have a look at it).
    2. Faulty plugins (although they would only affect 1 – 2 scripts, not all), so this is less likely to be the case. Best practice here is to bulk disable all plugins (by renaming the plugins folder to _plugins and going to Dashboard->Plugins. WP will inform you that it has disabled all plugins because he couldn’t find their files. You can rename the folder back to plugins but now all plugins are disabled. Check if your theme loads ok. If it does, Enable plugins one by one and Ctrl+F5 (Force refresh) your homepage until you find the culprit.

    Once we cover these steps we can go to other possible cases.

    A child theme is an extension of the parent. It does not replace the parent. It depends on it. The only purpose of the child theme is to host modifications to the parent theme that are “protected” from parent theme updates.

    And the principle is pretty simple:
    Whenever WP needs a theme file, it first looks in the child theme for it. If it’s not there, it loads it from the parent theme. So whenever you want to modify a parent theme file, you have to copy it in your child theme, keeping the exact same folder structure and apply your mods to it.

    There are two files that do not apply to this rule: functions.php and style.css, both placed in the root of the child theme. These two files should only hold php and css additions, not the parent files code. As you add php or css custom code, for different functionality, you put it in these two files.

    This is simplistic, you should read the complete documentation on how to make a child theme on Customizr website.

    And yes, my advice still stands. You have deleted important parts of your parent theme, which are required for your website to function properly.

    You’re not wrong.

    At the time I thought pagination worked and I knew it was hooked to __after_loop, hence I didn’t want to reset the query before it, so removing the current function from the hook and running the action hook made perfect sense.

    Ref:

    And why use this? remove_action + do_action

    I was avoiding a stack overflow. The function was hooked to __after_loop. If I ran do_action(‘__after_loop’) inside it without removing it first from the hook I entered a recursive loop.

    Your Customizr theme is corrupted. Your website is not loading several important scripts, one of them being bootstrap.min.js. I bet there are a lot of other things that do not work as they should in your installation. Delete Customizr theme folder (/wp-content/themes/customizr/), download the latest version of the theme (the reddish button) and extract it in the folder mentioned above.

    Get back here if you run into any other problems.

    I read that topic, @d4z_c0nf.

    Still no link to the actual website. A lot of variables there and, without a link or a debug.log, they’re still unknown: version of WordPress, version of Customizr, version of mqtranslate, other plugins installed (especially caching ones), other plugins or modules with BootStrap libraries, contents of functions.php, other files in child theme. Any mod to parent? A debug.log, maybe?

    This is information one should have access to, when trying to debug, if you ask me.

    Yes, I tried zooming both in and out in IE and it’s all sound.

    FYI, i’m using v 11.0.9600.17126, Update Version: 11.0.9(KB29257689), on Windows 7 Ultimate.

    If you have a lower version, maybe you should try updating. As already mentioned, it’s pixel perfect.

    The only problem is that you removed my CSS code and I can, once more, see the lower picture cut at the bottom when the hover is in its max state. The imgs are all 236 x 219px (when viewed full screen on a 1440 x 900 wide monitor, with text magnification reset to 0), except for the middle one that is 236 x 236px.

    By the way, do you happen to have some custom system settings regarding font smoothing, readability or anything symilar on your system? As in operating system properties… Those might be the root of this, as normally they should affect IE, since they share the same manufacturer.

    Also, afaik IE might have some readability settings which I think I turned off. Check those too.

    Have you tried google yet?
    Custom search page or Plugin.
    Custom 404 or Plugin.

    By the way, the theme already has both: http://www.thakuralelectric.com/?s=something and
    http://www.thakuralelectric.com/404. Unfortunatelly, it looks like you somehow managed to remove/disable the 404 template.

    I’d have to look into that particular case, for me it worked in every single site I applied this patch to. Might be mqtranslate or customizr version related, I have no idea.

    Or maybe he also changed qtranslate to mqtranslate in the

    current_theme_supports( ‘qtranslate’ )

    condition, which would be wrong, as it would return false in Customizr. But again, I’m shooting blindfolded here. I’d have to look.

Viewing 15 replies - 91 through 105 (of 681 total)