Issue with last wordpress (4.2.4) and Boldr Pro 1.6

[CEDRIC]

Hey there,

I was running fine Boldr Pro 1.6 on my blog, but today after the wordpress upgraded to 4.2.4; I just got my visual totally crashed

http://www.e-sk8.fr

Some characters are not even displayed fine (especially latin characters); no more logo; everything crashed visually.

I switched to boldr lite .. it was better (but of course all my layout was not good), but have character issues. I want back to BoldR… and you know what… all the configuration has been cleaned… I am really pissed because it seems this is not stable.

I downloaded a Theme Check to check the compatibility of the theme with wordpress… the list of issues is huge.

well, not happy. I need to get my blog back.

RECOMMENDED: Text domain problems in settings.php. You have not included a text domain!
Line 1620: ‘desc’ => __(‘Loads webfonts with the chosen subset. Latin-ext improves support for s
WARNING: The theme uses the add_shortcode() function. Custom post-content shortcodes are plugin-territory functionality.
WARNING: The flexible-width and fixed-width tags changed to fluid-layout and fixed-layout tags in WordPress 3.8. Additionally, the responsive-layout tag was added. Please change to using one of the new tags.
WARNING: Found base64_encode in the file icefit-options.php. base64_encode() is not allowed.
Line 34: return base64_encode ( gzdeflate ( serialize( $export_array ) ) );
WARNING: Found base64_decode in the file icefit-options.php. base64_decode() is not allowed.
Line 273: $output = unserialize ( gzinflate ( base64_decode ( $data ) ) );
WARNING: curl_init was found in the file functions.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 808: if (function_exists(‘curl_init’)):
Line 809: $ch = curl_init();
WARNING: curl_exec was found in the file functions.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 814: $output = curl_exec($ch);
REQUIRED: The theme uses the register_taxonomy() function, which is plugin-territory functionality.
REQUIRED: The theme uses the register_post_type() function, which is plugin-territory functionality.
RECOMMENDED: Screenshot size should be 880×660, to account for HiDPI displays. Any 4:3 image size is acceptable, but 880×660 is preferred.
RECOMMENDED: Possible variable $post_id found in translation function in icefit-testimonials.php. Translation function calls must NOT contain PHP variables.
Line 242: $output .= __( get_post_meta( $post_id, ‘icf_testimonial_company’, true) ).’</span
Line 325: echo __( get_post_meta( $post_id, ‘icf_testimonial_company’, true) ), ‘</spa
RECOMMENDED: Possible variable $post_id found in translation function in icefit-testimonials.php. Translation function calls must NOT contain PHP variables.
Line 241: $output .= ‘‘;
Line 324: echo ‘‘;
RECOMMENDED: Possible variable $post_id found in translation function in icefit-testimonials.php. Translation function calls must NOT contain PHP variables.
Line 239: $output .= ‘<span class=’testimonial-author-position’>’. __( get_post_meta( $post_id, ‘icf_testimonial_position’, true) ).'</span>’;
Line 322: echo ‘<span class=’testimonial-author-position’>’, __( get_post_meta( $post_id, ‘icf_testimonial_position’, true) ), ‘</span>’
RECOMMENDED: Possible variable $post_id found in translation function in icefit-testimonials.php. Translation function calls must NOT contain PHP variables.
Line 238: $output .= ‘<span class=’testimonial-author-name’>’. __( get_post_meta( $post_id, ‘icf_testimonial_client’, true) ).'</span>’;
Line 321: echo ‘<span class=’testimonial-author-name’>’, __( get_post_meta( $post_id, ‘icf_testimonial_client’, true) ), ‘</span>’;
RECOMMENDED: Possible variable $caption found in translation function in slider.php. Translation function calls must NOT contain PHP variables.
Line 55: ?><div class=’flex-caption’><?php echo __( $caption ); ?></div><?php
RECOMMENDED: No reference to add_theme_support( “title-tag” ) was found in the theme. It is recommended that the theme implement this functionality for WordPress 4.1 and above.
RECOMMENDED: No reference to add_theme_support( “custom-header”, $args ) was found in the theme. It is recommended that the theme implement this functionality if using an image for the header.
RECOMMENDED: No reference to add_theme_support( “custom-background”, $args ) was found in the theme. If the theme uses background images or solid colors for the background, then it is recommended that the theme implement this functionality.
INFO: Possible hard-coded links were found in the file functions.php.
Line 837: echo ‘<div class=’updated’><p>Thank you for using BoldR Pro ‘.$version.’! A new update (version ‘.$update[‘version’].’) is available to download from your member area on Iceable Themes</a
INFO: Non-printable characters were found in the index.php file. You may want to check this file for errors.
Line 150: if ( null != get_next_posts_link() ||��null != get_previous_posts_link() ):
INFO: At least one hard coded date was found in the file single.php. Consider get_option( ‘date_format’ ) instead.
INFO: At least one hard coded date was found in the file index.php. Consider get_option( ‘date_format’ ) instead.
INFO: settings.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 13: include_once(‘icefit-options.php’);
INFO: iframe was found in the file slider.php iframes are sometimes used to load unwanted adverts and code on your site.
Line 68: ?>

<iframe id=’player_<?php echo $post->ID; ?>’ class=’vimeo_slide video’ src=’
INFO: icefit-options.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 132: include_once(‘webfonts-list.php’);
INFO: editor-buttons.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 13: include_once(‘visual-shortcodes/visual-shortcodes.php’); // Visual Shortcod

[CEDRIC]

anyone?

[iceable]

Hello,

I do understand the frustration and hope we can get this sorted quickly.

– The issue does not seem to come from the theme itself; I could not reproduce such issue on a test site with WP 4.2.4
– From your description and what I can see on your site, it seems that something went wrong in the database (things sometimes go wrong during WordPress updates, this is why it is highly recommended to always backup your site before any update, and to make backups on a regular basis anyway especially since WordPress now includes automatic updates)
– When I look at the source code of the page, I can see the same broken characters, meaning the issue is not just with the display but the text itself as stored in the database does contain these characters.
– Configuration: BoldR Lite and Pro share the same configuration array in the DB so when you switch from Lite to Pro, your setting are still here. But if you switch back to Lite and save theme options, you actually erase the Pro related settings.

Do you have a recent backup of your site ? If so I suggest you restore the database from it to come back to a previous state before things went wrong.

Otherwise things will need to be repaired manually, which I can offer to help you with; especially with the broken character thing.

What else is wrong on your site by the way, except from the broken characters ?

---

As for the “theme check” plugin, please note that it does not exactly check compatibility with WordPress itself, but fitness with the “required guidelines” for a theme to be in included in the WordPress.org free themes repository.
BoldR Pro, as most premium themes, uses functions and methods that are not allowed in the repository to offer more functionalities, instantly making this plugin go mad.
I did carefully review each line you posted above, and I can guarantee nothing prevents the theme from working correctly.

Just to name a few: – curl is used for update check. Theme in WP.org do not need this since WP itself checks for updates in the repo, premium themes need their own way to check for update.
– base64_encode is not allowed in the repo because it is mostly use to obfuscate some “bad” code. Here it is used to encode the settings for the “import/export” settings option
– Custom posts and taxonomies (used for the slider, portfolio, testimonials, partners etc. in this theme) are considered “plugin territory” on WPorg, so it is not allowed to include these in themes hosted in the repo.
Etc.

[CEDRIC]

thanks for your support. I do agree with your approach. I assume that this is wordpress upgrade problem. By default updates are automatic (and no backup is done before launching automatically the upgrade)… and I am now fully stuck.

how can I correct the characters in the database? just for all the existing articles?

that would be great from you 🙂

[iceable]

What if you try to edit your articles (as you would normally do from wp-admin), can you see these broken characters in the editor ? If so you can replace them appropriately directly from there, so you don’t have to mess with the database itself.

But before you do so, I’m a bit worried that other parts of the DB could be broken as well and cause further issues.
Can you ask your host just in case they have a recent backup ? Not sure they do but asking doesn’t cost much, and if there is anyway they can revert your database to its previous state this would really be the best solution.

Otherwise, I would suggest the following steps:

– Backup your content right now, (you can use “Tools > Export” from wp-admin to save your contents) before things get worse.
– Backup your database also, even though its somewhat broken, better having this than nothing
– Then you try to repair the database with WP built-in function:
– Via FTP, edit wp_config.php and add this line at the end:

define('WP_ALLOW_REPAIR', true);

– Then go to yoursite.com/wp-admin/maint/repair.php to use the database repair function
– If it works you can then edit wp-config.php again and remove this line and you are done!
– If it doesn’t you can also try to use the repair functions on the database directly from phpMyAdmin

If it still doesn’t help, a more extreme approach would be to empty the database completely (after backing it up of course!) from phpMyAdmin: select all tables > Drop tables.
If you do that and go back to your site, you should see the WordPress one-click install page; just follow the instructions to re-install WordPress and it will rebuild a clean database.
Then go to “Tools > import” to re-import your posts (since you have previously exported with Tools > Export) to get your contents back. You will then need to re-activate your theme and plugins, and review your settings since everything they will be completely reset.

I hope you can get this sorted; let me know if you need any help, this is not really theme support but I can still give a quick hand.

---

On a side-note, the new automatic WordPress updates are twofold: on one hand they allow to push important security patches to all sites almost instantly, avoiding old sites with vulnerabilities to hang around. On the other hand, users have no control over it and when things go wrong they just cannot see it coming and this creates annoying situations.
This doesn’t happen very often, but every once in a while bad things just happen, especially when dealing with databases.

Although there is no perfect solution for everything, I think the most important step is to educate users to backup their sites on a regular basis, because restoring one is the best way to deal with a broken site after a failed update, server crash, hacking and other bad things that just happen sometimes.

[CEDRIC]

thanks, problem is that when I try to edit an old article it is not displayed in the editor, everything is blank. I think I could solve this if I was able to edit directly the articles in phpmyadmin to remove the weird characters

[iceable]

Well if you cannot access the editor’s page, then the problem is far worse than just these messy characters in the content.
Please refer to the rest of my last reply for suggested directions to hopefully be able to repair your WordPress install.

[iceable]

Hello,

Your site looks like it’s back on tracks with WP 4.2.4 and BoldR Pro 1.6, so I guess you managed to rescue everything ?
Please let me know if you are facing any further issue I can help with.

And if everything is fine now, it goes without saying that I strongly recommend you start making backups of your site, so you’ll be prepared in case anything else goes wrong in the future!

I’m considering writing an article/tutorial about backing up WP sites since that’s a pretty important matter. In the meantime there are quite a lot of guides that can be found through google, and even a few plugins that make it even easier to backup your site right from wp-admin.

[Author]

Posts