Forum Replies Created

Viewing 15 replies - 1 through 15 (of 26 total)
  • Thread Starter Jurjen

    (@jurjen)

    Removed all the WP Rocket stuff from the .htaccess: it fixed the issue.

    So now I need to figure out how to fix this WP Rocket bug.

    Thread Starter Jurjen

    (@jurjen)

    I cleared the Rocket cache and OPcache, it didn’t fix it.
    I disabled the plugin, it didn’t fix it.

    Thread Starter Jurjen

    (@jurjen)

    I did clear the Rocket cache earlier today. Will verify that I’m doing a full clear and will try to disable the plugin before removing.

    Also: my redirect works properly on Firefox, just not on Chrome.

    Corpo has been deleted as a theme and the creator shut down her personal website and doesn’t seem to offer support anymore.

    It’s a pity, I love her theme!

    Even though the page is shut down, the physical file is still present on the WordPress servers: https://ww.wp.xz.cn/themes/download/corpo.1.3.2.zip

    Thread Starter Jurjen

    (@jurjen)

    Found it in one of the php pages under rewrite.

    Thread Starter Jurjen

    (@jurjen)

    Here’s the theme support code in Functions.php:

    add_theme_support( 'custom-background', array(
    		'default-color'			=> 'CECECE',
    		'default-image'			=> get_template_directory_uri() . '/images/background.jpg',
    		'default-repeat' 		=> 'no-repeat',
    		'default-position-x' 	=> 'center',
    		'default-position-y' 	=> 'center',
    		'default-attachment' 	=> 'fixed',
    		'wp-head-callback' 		=> '_custom_background_cb', )
    	);

    Thread Starter Jurjen

    (@jurjen)

    I don’t think the theme is the culprit. The installation is fresh any way and I don’t have any other plugins.

    As mentioned, the metabox is loaded and I noticed in your code it checks that there is no conflict in the variables you used. So if there were to be a conflict, it wouldn’t load the meta box.

    I just replaced the php files of your plugin one by one, nothing is fixing the issue.

    It is simply not writing to the SQL database.

    It’s easy. Open inc/class-custom-backgrounds-filter.php

    Then, look for:

    /* Output the custom background style. */
    		echo "\n" . '<style type="text/css" id="custom-background-css">body.custom-background{ ' . trim( $style ) . ' }</style>' . "\n";

    And replace it by:

    /* Output the custom background style. */
    		echo "\n" . '<style type="text/css" id="custom-background-css">
    	body.custom-background{ ' . trim( $style ) . '
    	-webkit-background-size: cover;
    	-moz-background-size: cover;
    	-o-background-size: cover;
    	background-size: cover;}</style>' . "\n";

    Thread Starter Jurjen

    (@jurjen)

    That would be only on the contact page. On the other pages, this shouldn’t cause any bug using the contact form through the footer.

    Also, I think this bug only surfaces in Google Chrome, as one of my testers using Chrome mentioned it. However, I don’t have this bug in FireFox and IE.

    But, I’ve removed the recaptcha so you can try some things.

    I’ve noticed another bug while changing the settings though (not sure if it’s in the plugin or the WordPress back-end though): if I enter multilingual content in the message boxes, it will save correctly, however it doesn’t load all the content afterwards.

    Example: in the box for “Message sent header” I’ve entered: [:en]Message sent![:fr]Message envoyé![:nl]Bericht verzonden!. It saves correctly (it shows in the SQL database and loads correctly in the contact form), but revisiting the contact form admin page, it only loads the French texts. (So now it just shows Message envoyé! in the Message sent header box.)

    Thread Starter Jurjen

    (@jurjen)

    No, as mentioned, the lightbox is in the contact section in the footer area. The contact page was made as a backup if the footer popup wouldn’t work properly when the site will be ready to launch.

    Thread Starter Jurjen

    (@jurjen)

    This is the plugin: https://ww.wp.xz.cn/plugins/wp-colorbox/

    Yes, the AJAX validation has been activated in the settings.

    I could send a link to my test page via email, I’d rather not put it here since I don’t want Google to index it yet.

    Thanks!

    Thread Starter Jurjen

    (@jurjen)

    Fixed by adding these two lines as well to mqtranslate_hooks.php (look for // Hooks (execution time non-critical filters)):

    add_filter('post_type_link',				'qtrans_convertURL');//fix custom post type URL
    add_filter('post_type_archive_link',		'qtrans_convertURL');//fix custom post type archive URL

    Two possible quick work-arounds:

    1) use the HTML character for the apostrophe: &rsquo;

    2) copy-paste another, simular looking, symbol from Windows’ Character Map application.

    Yes, you’ll manually need to edit one of the templates.

    Open this file: wp-content\plugins\corpo_toolkit\templates\single-corpo_portfolio.php in any decent text editor.

    Replace this part (on line 84):
    <a href="<?php echo get_post_meta($post->ID, 'corpo_projectURL', true); ?>"><?php echo get_post_meta($post->ID, 'corpo_projectURL', true); ?></a>

    …with this:
    <a href="<?php echo get_post_meta($post->ID, 'corpo_projectURL', true); ?>" target="_blank"><?php echo get_post_meta($post->ID, 'corpo_projectURL', true); ?></a>

    It’s the target="_blank" that will do the trick.

    Thread Starter Jurjen

    (@jurjen)

    Indeed, the do_shortcode made it work in the end! Unfortunately the translations didn’t work any more after that.

    I ended up replacing your shortcode by the actual HTML code it should output to make it work with the translations: <a class="wp-colorbox-inline" href="#contactbox"><?php _e('translated texts'); ?></a>

    Not sure if you can improve this for future versions, but I just wanted to give you the feedback.

    And I’m glad you but me on this track since I needed the do_shortcode to make the shortcode work that I wanted to put inside the colorbox. 😉

    Thanks again!

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