20 NOV 2014 - WP 4.0.1 AUTO UPDATE = OH NOooooo!!

1) The WP 4.0.1 update, which auto installs on many user sites (unless you were smart enough to not trust WP and not allow such auto updates) has broken some shortcodes such as the Process Steps Shortcode.

WordPress is now auto- texturizing inline styling in some shortcodes :

<i class=icon-pencil style="color:#2ac4ea"></i>
<i class="icon-”pencil”" style="color:”#2ac4ea”"></i>

Notice that WordPress unnecessarily added extra quotes into the shortcode string rendering it unreadable.

WordPress also is impacting complex shortcode strings where shortcodes are multilevel. For Example in wp 4.0 this worked fine if only the tabs shortcode was registered

[tab title="the title" icon="home"]

But in wp 4.01 this fails as when the subcode ([tab title="the title" icon="home"]) which is part of [tabs] is not registered as a "legal" shortcode itself. The parent shortcode called "Tabs" can access the [tab] shortcode but gets a different (texturized) array back when reading the code within its container holding the shortcode. All the strings that are parsed have a different format causing it subsequently to fail from working. This means that encapsulated (complex) shortcodes now needs to be registered even for the shortcodes within the shortcode holder.

So all our container shortcodes like, carousel, tabs, accordion, process steps etc. are affected by this update.

BTW, we are aware of no valid security reason for this change, and in our opinion a change like this should have had plenty of lead time and be part of a major update, not an "on the fly" security update which many users will have not disabled.

It is not necessary to make further reports about shortcodes not functioning if your site auto-updated to wp 4.0.1. We are working on updating our new MultiFlex build 1.2 and anticipate it's availability with the changes to accommodate WP 4.0.1 likely in the Sunday/Monday timeframe.

2) We are starting to roll out some paid design services per requests from users.   Please visit UPDATE SERVICES to view the first service group we have put in place which are for those who would like someone else to handle updates.  Please review them and see if any might be beneficial for you.  Of special note, if you are still using the Striking Original theme because you have been reluctant to update due to your knowledge base, now we can implement the update for you on a guaranteed results basis.

More services for Site Optimization, Site Tuning, Security, and Design shall be rolled out in the forthcoming days.

3) Rev Slider Plugin Security Vulnerability - Old News!  Its starting to filter out onto the net that a long time ago the Rev Slider Plugin had a security vulnerability.  This was patched and included in all the MultiFlex 1.0.2 betas and the eventual 1.0.2 official release throughout March 2014.  So any theme version 1.0.2 or later in which the Rev Slider plugin is active is secure.  We are always preaching update, update, update, so if you have not updated to a more current version of the theme, what are you waiting for?

As long as you have updated your MultiFlex site, and not been ignoring those update notices in your theme dashboard for the last 7 months, you are long since covered.  We can't imagine anyone is still running the test theme Striking Responsive from 2013, but if you are you should update to the latest MultiFlex version although not all the "striking Responsive" theme betas included a version of the rev slider that was vulnerable.

4)  Striking 5.3.1 (aka Striking Original theme) for users continuing to use the non-responsive framework was released on August 24, 2014..  It will only available by the internal update function as this theme is deprecated and no longer available for sale. If you are still using the Striking Original theme the update notice should now be showing in your site and you should update at your convenience.

James on behalf of the Striking Team
To insert code in a forum thread or comment wrap it in code tags: <code>...</code>.


The theme documentation both inline and written is very extensive covers many of the questions we see asked repeatedly on the forum. Thus we request that before you post a new thread on the forum, you review the documentatoin and also do a search of the forum as your question already has been covered and thus answered by one of those 'superb' tutorials/video's we made.

You can find the documentation and video tutorials here : StrikingR Documentation/Videos

If that does not answer your question try todo a google search of the forum. Search for :

"Kaptinlin.com support [the question]"

Because google indexes our forum pretty well and probably almost every question you are having has been asked and answered you most likely will find the answer to your question by that search. If not then please post a new forum thread with your question (each question in its own thread).

CUSTOMIZATION - Please remember that while we are perfectly willing to help out with a simple tweak here and there in respect of customization, most css customization, and all php and js customization, and plugin integration matters, fall into the paid support category. By all means post on the forum, as other users may assist, and we will try to point you in the right direction when we can.

Steps to take before posting a thread

Do you see the issue on our demo website? Striking Multiflex Demo Website If so, please send us a url to that page in your thread. If not please walk through the steps below before posting a thread.

1) Make sure you are using the latest version of the theme. You can check that either at themeforest at the account you bought the theme with or by turning on the update notification in the theme advanced settings. If you are using the latest build please try to download the latest version again from themeforest, unzip it and re-upload the theme by usage of ftp upload overwriting the one that is in there to rule out any wrong theme code or custom adjustsments you made which could be interfering.
2) Undo all hardcoded theme adjustments (php, html, or css)
3) Remove any (manually) added (java) scripts in the theme settings, theme core files or widget area's
4) Turn off the child-theme
5) Clear the striking cache in the striking advanced settings
6) Clear cache in your browser you are using
7) Turn off minify and/or cache plugins
8) Turn off all your plugins and see if the issue resolves.
9) Use google to search the forum for your burning question first as most questions already have been asked and answered. Search for kaptinlin.com support [your question]

Now when you do post a thread include :
1) A url to the website and or problem page so we can see the issue and investigate the code.
2) The code used causing the problem so we can replicate the issue.



1)  Weekend hours

Be advised that weekend forum support is limited to Saturday up to 3pm EST after which any questions posted, if not assisted by other users, would normally be dealt with on the following Monday.


PLEASE -> if you have not given Striking a star rating at Themeforest, please log into your account, go to your downloads page, and give us a Star Rating - hopefully 5 stars!  every 5 star rating has a big impact upon us (and 4 star ratings and below are hugely detrimental - it takes twenty 5 star ratings to overcome one 4 star rating).

Right now, we have the most per capita in the marketplace of any top selling theme.   If even 10% of our users who have not yet rated us were to give us a 5 rating, we would be overjoyed. Please give this consideration on our behalf.  

Since its release Oct 2010, Striking has had 60+ separate updates of NEW features, more than any other theme in the Themeforest marketplace. Striking is dedicated to keeping its users up to date with the Wordpress core, and the latest features available in the Wordpress theme world.

Striking Team