Implicit

Contents

1. Weird page builder layouts happening

2. Update Log (Implicit)

3. Theme completely broken without any code changes (something regarding XML or file_get_contents)

4. What are the server requirements to run this theme?

5. Can't create a child theme

6. Twitter or Google+ count showing -1

7. I cannot save my theme options. The loading wheel just keeps spinning and the save never completes.

8. After updating to 1.2 I get a bunch of PHP warnings on my page.

9. Tabs, Toggles, and Accordions titles do not display correctly after WordPress 4.0.1 update

10. How do I translate the theme into another language?

11. I'm using WordPress 4.5 and/or PHP7 and my theme is broken.

12. Support Policy

13. Social counts stopped working

14. A note on theme updates.

1. Weird page builder layouts happening

Make sure there are not any pages in your "trash" that have the "category front page" layout option with a selected category.

2. Update Log (Implicit)

To update your theme:

Automatic

Manual


PENDING - 1.8

This update is purely a maintenance/bug fix update to make the theme compatible with the latest versions of PHP and WordPress. There are no new features provided with this release.

Files Modified:

  1. style.css (only the version number at the top was changed)
  2. functions/admin/metaboxes-generator.php
  3. functions/admin/shortcode-generator.php


8/2/2016 - 1.7

This update is purely a maintenance/bug fix update to make the theme compatible with the latest versions of PHP and WordPress. There are no new features provided with this release.

Files Modified:

  1. style.css (only the version number at the top was changed)
  2. functions/admin/option-generator.php
  3. functions/widgets/*.php (all files in this folder were modified)


6/6/2015 - 1.6

Files Modified:

  1. style.css (only the version number at the top was changed)
  2. functions/core.php
  3. functions/theme.php
  4. functions/widgets/widget-social-counts.php
  5. inc/page-content.php

12/17/2014 - 1.5

Files Modified:

  1. style.css (only the version number at the top was changed)
  2. framework.php
  3. functions/core.php
  4. functions/loop.php
  5. functions/reviews.php
  6. functions/admin/it-options.php
  7. functions/admin/metaboxes-generator.php

11/26/2014 - 1.4

Files Modified:

  1. style.css
  2. framework.php
  3. functions/ajax.php
  4. functions/core.php
  5. functions/reviews.php
  6. functions/theme.php
  7. functions/admin/core.php
  8. functions/admin/option-generator.php
  9. inc/css.php
  10. inc/page-content.php
  11. inc/sticky.php
  12. js/ajax.js
  13. js/ajax.min.js

8/28/2014 - 1.3

Files Modified:

  1. style.css
  2. archive.php
  3. functions/core.php
  4. functions/loop.php
  5. functions/theme.php
  6. functions/admin/it-options.php
  7. functions/admin/meta-page.php
  8. functions/admin/meta-post.php
  9. functions/admin/option-generator.php
  10. functions/admin/assets/js/admin.js
  11. functions/shortcodes/connect.php
  12. functions/shortcodes/headliner.php
  13. functions/shortcodes/html.php
  14. functions/shortcodes/loops.php
  15. functions/shortcodes/menu.php
  16. functions/shortcodes/scroller.php
  17. functions/shortcodes/topten.php
  18. functions/shortcodes/trending.php
  19. functions/shortcodes/widgets.php
  20. inc/nav.php
  21. js/ajax.js
  22. js/ajax.min.js

8/5/2014 - 1.2

IMPORTANT NOTE: This is a major update and significantly changes the way the page builder system works, and thus will require you to re-setup any areas in your theme options where you have previously used page builders. We highly recommend making a site backup before updating to avoid losing any page builder configuration!

Files Modified:

  1. style.css
  2. 404.php
  3. archive.php
  4. bbpress.php
  5. buddypress.php
  6. footer.php
  7. index.php
  8. page.php
  9. search.php
  10. single.php
  11. framework.php
  12. template-authors.php
  13. template-directory.php
  14. inc/css.php
  15. inc/directory.php
  16. inc/page-content.php
  17. functions/ajax.php
  18. functions/core.php
  19. functions/loop.php
  20. functions/theme.php
  21. functions/admin/it-options.php
  22. functions/admin/meta-page.php
  23. functions/admin/meta-post.php
  24. functions/admin/option-generator.php
  25. functions/admin/assets/css/admin.css
  26. functions/admin/assets/js/admin.js
  27. functions/admin/scripts.php
  28. functions/widgets/widget-latest-articles.php
  29. functions/widgets/widget-list-paged.php
  30. functions/widgets/widget-review.php
  31. functions/widgets/widget-sections.php
  32. functions/widgets/widget-top-reviewed.php
  33. functions/widgets/widget-top-ten.php
  34. functions/widgets/widget-trending.php
  35. js/ajax.js
  36. js/ajax.min.js
  37. lang/en_US.po and .mo

Files Added:

  1. functions/shortcodes/connect.php
  2. functions/shortcodes/loops.php
  3. functions/shortcodes/headliner.php
  4. functions/shortcodes/html.php
  5. functions/shortcodes/menu.php
  6. functions/shortcodes/scroller.php
  7. functions/shortcodes/topten.php
  8. functions/shortcodes/trending.php
  9. functions/shortcodes/widgets.php

Files Removed:

  1. inc/connect.php
  2. inc/grid-infinite.php
  3. inc/grid-paged.php
  4. inc/list-infinite.php
  5. inc/list-paged.php
  6. inc/headliner.php
  7. inc/html.php
  8. inc/menu.php
  9. inc/scroller.php
  10. inc/top-ten.php
  11. inc/trending.php
  12. inc/widgets.php

7/28/2014

Files Modified:

  1. style.css
  2. functions/theme.php
  3. functions/admin/it-options.php
  4. functions/shortcodes/video.php
  5. inc/css.php
  6. inc/grid-paged.php
  7. inc/grid-infinite.php
  8. inc/list-paged.php
  9. inc/list-infinite.php
  10. js/ajax.js
  11. js/ajax.min.js
  12. js/scripts.js
  13. js/scripts.min.js

7/18/2014

Initial Release

3. Theme completely broken without any code changes (something regarding XML or file_get_contents)

First of all, we are very sorry for this sudden inconvenience! It couldn't have come at a worse time, what with me being out of town on a family vacation this week :(

It's actually a very simple fix though to get your site back up and running.

Youtube recently changed its API for the youtube subscriber count mechanism. Go into your social counts widget anywhere it is present within your theme's widget panels and disable the youtube subscriber count option (you can leave the other social count options enabled). We will be rolling out updates with the fix as soon as we are able to.

Most likely we will be completely removing the youtube social count component from the theme in favor of using a plugin instead, since technically this is plugin territory rather than theme territory anyway.

UPDATE

We have fixed all of our themes where this was an issue. Please update your theme which will fix this issue.

4. What are the server requirements to run this theme?

  1. PHP 5.0+
  2. WordPress 3.8+
  3. cURL must be enabled on your web server. Your web host can do this for you, just ask them. Or you can refer to this link which shows you how to do it: http://stackoverflow.com/questions/1347146/how-to...
  4. You need to have allow_url_fopen set to on. Your web host can turn this on for you, just ask them. Or you can refer to this link which shows you how to do it: http://www.php.net/manual/en/filesystem.configurat...
  5. Increase your max_input_vars setting on your web server to at least 2,000. Your web host can do this for you, just ask them. Or you can refer to this link which shows you how to do it: http://stackoverflow.com/questions/10303714/php-ma...

Note: If you are using a one-click script-installed WordPress installation (rather than their official WordPress installation instructions) such as GoDaddy or similar, you will potentially need to edit a different file to increase your max_input_vars variable. Here is their knowledge-base article regarding this file:

https://support.godaddy.com/help/article/8913/what...

Note 2: If you have checked all of this and the settings still won't save, it could be because your web host has a firewall called ModSecurity enabled for your domain which is detecting an SQLi type of possible attack when the theme options are saved. Try having your host disable the ModSecurity and see if that helps.


5. Can't create a child theme

If you're having an issue creating a child theme, please see this ticket with an alternate solution: https://industrialthemes.ticksy.com/ticket/494876/

6. Twitter or Google+ count showing -1

The Twitter count is because of a resource limit being hit on our Twitter app. This needs to be updated within the theme files, but we're not sure when this will be applied. In the mean time please use a plugin for your Twitter count rather than the theme's built-in counter.

For Google+, we have isolated the cause of this and hope to fix this in the next theme update. Again, in the mean time, use a plugin instead.

Users report the following plugin displays social counts correctly: https://wordpress.org/plugins/social-count-plus/

7. I cannot save my theme options. The loading wheel just keeps spinning and the save never completes.

You need to increase your max_input_vars setting on your web server to at least 2,000. Not to worry if this sounds daunting, it's actually a very easy fix, and your web host can do it for you if you don't know how - just ask them. You can also refer to this link to increase this setting yourself: http://stackoverflow.com/questions/10303714/php-ma...

Note: If you are using a one-click script-installed WordPress installation (rather than their official WordPress installation instructions) such as GoDaddy or similar, you will potentially need to edit a different file to increase your max_input_vars variable. Here is their knowledge-base article regarding this file:

https://support.godaddy.com/help/article/8913/what...

GoDaddy Users:

In your site root (commonly the public_html folder) you must create the php.ini file and add the following lines to it:

max_input_vars = 5000
suhosin.post.max_vars = 5000
suhosin.request.max_vars = 5000

Additional help: The following is from an Engine user who still had issues with the spinning loader but was able to get it working via the following:

If you were migrating your database or complete site from WAMP 2.0 and/or using the “all-in-one-wp-migration” plugin, the following steps might be necessary:

1) Clear out your WordPress database via phpMyAdmin on your web server (drop all tables so it's empty).

2) Export your local database

3) Import the database to your web server

4) Don't forget to assign correct user for the DB you are migrating (your DB username on WAMP2.0 is most likely "root" and password is blank. It must be changed.)

8. After updating to 1.2 I get a bunch of PHP warnings on my page.

Edit the functions/shortcodes/loops.php file and locate lines 136 and 381 which are both identical and should look like this:

if(!empty($disabled_filters)) $disabled_filters = explode(',',$disabled_filters);

Change them both to this:

$disabled_filters = !empty($disabled_filters) ? explode(',',$disabled_filters) : array();

Next, edit the functions/admin/option-generator.php file line 1783:

$builder_name = $builder_array[$builder_id];

Change it to this:

$builder_name = array_key_exists($builder_id, $builder_array) ? $builder_array[$builder_id] : '';

Both of these issues will be permanently fixed in version 1.3.

9. Tabs, Toggles, and Accordions titles do not display correctly after WordPress 4.0.1 update

Edit your functions/core.php file and add this to the very end of the file, but before the closing ?> tag:

add_filter( 'no_texturize_shortcodes', 'it_shortcodes_exempt' );
if(!function_exists('it_shortcodes_exempt')) {
	function it_shortcodes_exempt($shortcodes){
		$shortcodes[] = 'toggles';
		$shortcodes[] = 'tabs';
		return $shortcodes;
	}
}

10. How do I translate the theme into another language?

I merely provide a translation-ready PO file with this theme that you can then take and translate using software such as Poedit (http://www.poedit.net/). I have not translated a WordPress theme myself, nor do I really know how to translate one, so I am not the best resource to help you with this specific task. I do know that the PO file I provide works, because hundreds of customers have successfully used it to translate their themes. To get much better information than what I can provide you, start with this resource: http://codex.wordpress.org/Translating_WordPress, and then ask any specific questions on WordPress Answers: http://wordpress.stackexchange.com/, or the WordPress support forums: http://wordpress.org/support/.

Flavor, Steam, and Explicit users:

Here are steps to translating the theme. Special thanks to Micha� Kowalski for compiling these steps!

1. Download and install Poedit
2. Open "en-US.po" file
3. Check a line you want to translate, and write a word in your language in Translation section.
4. If your translate is done, click File > Save as and name it correctly to your language, for example "pl_PL.po" for Polish language.
5. Then generate a .mo file clicking File > Save as, name it correctly to your language, for example pl_PL.mo, and thats it.
6. Upload these two files to your theme directory, "wp-contet/themes/THEME_NAME/lang" and you are done.

Alternative

If you have issues using Poedit you can try Transposh instead which has been used successfully by some IndustrialThemes customers.

11. I'm using WordPress 4.5 and/or PHP7 and my theme is broken.

Open the functions/admin/option-generator.php file and locate line 38 which looks like this:

$out .= $this->$option['type']( $option );

Change that line so it looks like this:

$out .= $this->{$option['type']}($option);

Next open the functions/admin/metaboxes-generator.php file and locate line 48 which looks like this:

$out .= $this->$value['type']( $value );

Change that line so it looks like this:

$out .= $this->{$value['type']}( $value );

Finally, open the functions/admin/shortcode-generator.php file and locate line 122 which looks like this:

$out .= $this->$option['type']( $option );

Change that line so it looks like this:

$out .= $this->{$option['type']}( $option );

Save the files and empty your caching (including caching plugins) and that should fix it.

12. Support Policy

Stop. Read. (It's Good For You!)

Before you create a new support ticket, please read through the documentation which is contained within the documentation folder inside of your theme folder. Within the theme options pages of the theme there are additional instructions and tips for each section and setting. There are also some very helpful tips in the FAQ's. (A link to each theme's FAQ is located in the item description on ThemeForest). Please read through both the documentation and the FAQ's before you create a ticket. We usually get the same 8 or 9 questions about our themes over and over, and that is why we have taken the time to write detailed solutions in the FAQ's to avoid having to write the same answers over and over.

If your particular issue is not found in the documentation or the FAQ's, please search the support center for a solution to your question. There are thousands of posts and users asking questions here, so it is very likely your question has already been asked and answered.

Create a Support Ticket

If your question has not been asked in a support ticket yet (or at least you can't find it anywhere), then please create a new ticket with your question. Be as specific as possible. It helps to provide a URL, screenshot, or a detailed explanation of your issue. However, please note that, due to the amount of time it takes us to develop, update, maintain, and support our themes, we are not able to perform customizations for our themes ("freelance" work).

What We Can Help With

Any questions about how the theme works and any bugs or errors you find are completely acceptable questions. This includes such things as which file some particular code is in, asking what things the theme can and can't do, asking about future updates and enhancements, pointing out if you found an error or a bug, etc.

What We Can Not Help With

ThemeForest does not require authors to give support in any way shape or form, nor does your purchase of a ThemeForest item come with any guarantee of support in any way. Regardless, we spend on average 14 - 28 hours a week supporting our themes via the support forums (just for reference, that's $1400 - $2800 worth of lost revenue each week). Why do we do that? Because we want to stand out among the crowd of authors in the marketplace, and we know that providing good support for a product says that we are confident in what we have developed.

That being said, we cannot provide support for anything outside the scope of theme support (we just don't have time!). This includes:

For example, if you post a question asking how to change the background color of the main content area of a theme, and the ability to do that is not already in the theme options page, we will unfortunately not be able to help with this.

Please Do Not Abuse Support

This support is completely free of charge, so please do not abuse it. Remember, you paid $40 - $50 for a working website theme which in some cases took up to 320 hours to build. That is a better deal than you'll get anywhere else. Expecting someone to additionally help you build your website to tailor-fit your needs for free is unrealistic, all things considered. The theme is well documented, and the code is indented, spaced, commented, and intuitively built specifically to enable you to make changes to your theme easily.

We want our themes to be highly-rated on ThemeForest. The only way to do that is to make sure our themes work well and our customers are satisfied. That is why we have spent so much time making sure this is the case. Making the theme as easy to use and as intuitive as possible for you actually helps us just as much as it helps you, so believe it when we say that is our goal!

A Note On Theme Customizations

Even if your customization seems super simple and you think it would only take a few minutes, it is important to note that if we helped one person, how would we justify not helping the next person? 100 people who need super simple customizations is not so super simple anymore. We get on average 15 requests a day for theme customizations, so it just wouldn't work for us to adopt this policy. Please check out Envato Studio (http://studio.envato.com/) or Elto (https://www.elto.com/?invite=industrial), which are great resources to hire a web developer who can help you with your customizations.

13. Social counts stopped working

You will need to use a plugin to display your social counts rather than the theme's built-in functionality. The vendors have all changed their APIs and this is now technically considered plugin territory rather than theme territory according to ThemeForest, so we are no longer offering social counts packaged with our themes. We will be updating all of our themes and completely removing all social count functionality as soon as we're able to. Thanks for your patience and understanding in this matter.

UPDATE:

A user recommended this plugin as an alternative: AccessPress Social Counter

14. A note on theme updates.

We are continuing to update all of our themes, even if it has been a while since our last update. To speed up this process, which will help everyone out, please adhere to the following guidelines:

1) Please do not ask when the next theme will be available. With so many feature requests and themes to update, it is impossible to know for sure when the next update will be completed.

2) Please do not ask what will be included in the next theme update. We are constantly adding items to the update list which grows longer every day, and consequently re-prioritizing the items to put the most critical items that affect the most people at the top of the list.

3) If you notice a theme bug or have a suggestion for a theme update, please open a new ticket with your issue and we will respond and add it to our list accordingly.

4) If we have responded to you stating something will be in the next theme update, then it will be (please do not continue to ask us over and over).

5) If we have responded to you stating we will add your request to the future possible update list, then it might be included in the next theme update, but there is no guarantee.

6) Please do not assume since a theme hasn't been updated in a while that we are not still planning on updating it in the future.

For your reference, here is how we prioritize our update list, from most important to least important:

1) Compatibility with the latest version of WordPress

2) Compatibility with the latest versions of supported/compatible plugins (WooCommerce, BuddyPress, and bbPress)

3) Functionality bugs and errors

4) Style/layout issues

5) New features and theme enhancements

6) One-off compatibility with third-party plugins