Another day, another release! As always, we're incredibly excited about this new update to X as well as the paired update with Cornerstone that brings some exciting new features to the fold. This time around we focused primarily on bringing new functionality to our WooCommerce integration. Specifically, we've added a navbar cart, which can be easily configured in many different forms and we have also improved the WooCommerce AJAX index behavior to provide greater feedback to our users.
The navbar cart is enabled via the WooCommerce section of the Customizer and features a variety of configuration options. Below is one example of the many end results you can achieve with the navbar cart as well as a list that quickly summarizes these newly available options:
The navbar cart will update in real time if you have the Enable AJAX add to cart buttons on archives setting turned on. Also, we have also included some new features for this setting as well to help make the shopping experience more fluid within X. If this WooCommerce setting is enabled, you will be able to utilize four additional options within the same section of the Customizer. These options can be found under the AJAX Add to Cart subsection, and they allow you to customize the colors of the various states for the AJAX confirmation animation that we have added to X:
Remember, this animation will only take place on your shop archive pages and you must have the setting previously mentioned enabled for it to work. Due to some of the considerations needed for these new elements, we have also added two new options to the Customizer: Navbar Top Link Spacing (px) and Navbar Letter Spacing (px). The link spacing option can be found under the Header section of the Customizer and allows you to now specify the spacing between top level links in your fixed or static top navigation. The navbar letter spacing option can be found in the Typography section of the Customizer and allows you to set the letter spacing of top level navigation items for greater control. These controls were needed to position various elements correctly in a dynamic manner and should be set for you automatically when upgrading. The previous setting for link spacing in Ethos has been removed in favor of this new global option.
We also made a minor tweak to how navbar links are positioned for Icon so that there is greater consistency across all Stacks. Because of this, after updating you will need to make sure to adjust your navbar link positioning to your desired position. Due to the nature of this setting, there was no way to automatically take care of this, and as it is a minor adjustment it shouldn't take long to get back in place.
We have some great new features and big performance improvements in store for you with this release of Cornerstone! Firstly, we have a brand new Revolution Slider element included in the builder now, making the use of your sliders easier than ever. Simply drag in your element where you want it and select the slider you would like to use from your current slider list, it doesn't get much simpler than that!
<head> by a whopping 93.44% and bring all styles and functionality under one roof (cue party music)!
Because of this streamlined video handling, users are now able to run multiple background videos at a time (only if absolutely needed, but we still strongly recommend that you do not utilize more than one on a page at a time for performance reasons). Also, the
[x_audio_player] shortcodes have been updated to accept multiple native sources of media at once via the new
src attribute (old attributes such as
ogv for video and
oga for audio have been deprecated in favor of this new method). All you have to do is input your multiple sources and separate them with a
| character, like so:
The format you want to use first should be placed at the beginning, with fallbacks towards the end (i.e.
.ogv for video or
.oga for audio). These multiple sources are not requred, they simply provide greater native reach in more suitable formats when available, lending a smoother experience for your users if desired. Similarly to the
src attribute on the shortcodes mentioned above, the
bg_video input for
[x_section] shortcodes works the same way, as do the background video inputs for the Slider Settings: Above Masthead and Slider Settings: Below Masthead meta options on pages.
On top of all these great new features and improvements, we have patched up a select number of little issues throughout the builder as mentioned in the sidebar summary. All in all, the building experience in Cornerstone continues to mature with each release and we are continually thrilled to see where it leads us.
Visual Composer has been updated to v.4.5.3 in this release of X due to XSS vulnerability in the prettyPhoto library. Within Visual Composer the prettyPhoto library has been updated v3.1.6, the latest stable and secure version. If you are not utilizing Visual Composer's shortcodes within X, there is no pressing need to download this update.
In this version of X we've made a select few updates to clean things up in the theme; however, the bulk of this release primarily has to do with changes to Cornerstone, which will be covered separately.
One simple but significant change we've made to this version is the addition of a new
_meta.php view located in
/framework/views/global/ of the theme. This view is hooked into the
<head> via the
wp_head action and serves as an easy way to manage general purpose, non-dynamic meta data needed for a site. This cleaned up our global
_header.php and now gives users multiple ways to add their own content here if needed by either hooking into
wp_head themselves or overwriting the
_meta.php view via a child theme, whichever is most comfortable to each user.
Additonally, we've put in a few CSS rules across all Stacks to ensure that any
<ol> that is the
:last-child (and a direct child) of the main
.entry-content element for posts and pages has its bottom margin removed to ensure no extra spacing is left at the end. Any of these elements that are added inside of another element will not be targeted and will need to be formatted manually if desired.
It has been a couple weeks since our last release of Cornerstone and we have included some exciting additions to this update as well as patching up some issues that were revealed after the initial launch.
We'll begin with the shiny new stuff! We have included a new Widget Area element into the builder, which allows users to output a widgetized area into the main content of your page. This was one of the most widely requested features from our users upon release, so we're thrilled to be able to be able to deliver it so quickly to everyone. Here's an example of what it looks like in action:
Additionally, for longer pieces of text users have wanted to be able to expand the content controls in Cornerstone (as well as the code editor). We have added these features in as well, so now any WordPress editor control or standard
<textarea> in the Cornerstone sidebar can be expanded. To do this, simply click the Expand button below the control:
This will make the editor slide to the side and ultimately appear over the preview area. This allows users who are writing longer content to take full advantage of this space while needed and to more easily format text. It will appear like so once the animation is complete:
As for other general updates, we have opened up the element mapping API within the plugin, allowing users to input their own custom shortcodes as desired. We will have documentation on this released as soon as possible so that our users can take full advantage of this powerful feature. We have also updated Modernizr in the plugin to v3.0.0 for improved featured detection and also to address some styling bugs for certain elements, such as the Card element in Internet Explorer. Speaking of the Card element, we have also added new parameters to specify the flipping direction of the element as well as swap out the icons on the front face for an image if desired.
All in all, this was a very well rounded release that tackled some big bugs along with introducing some fantastic new features into the mix. We hope you all enjoy and we're looking forward to getting our next round of Cornerstone features and improvments out to you all!
It has been an exciting couple of days since our v4.0.0 release of X and Cornerstone, our brand new, shiny, frontend page builder! We are already receiving some tremendous feedback from our users and we are looking forward to incorporating items that we feel will work to improve the overall experience in the plugin. So far the fastest update we've heard of is someone building their homepage in Cornerstone in a little over an hour with no prior use of the tool. Wow!
Regarding Visual Composer integration, we would like to make things abundantly clear: our users can rest assured that there will be no timeframe on "migrating" away from Visual Composer and can continue to utilize the plugin as they always have. Users have the choice between completely native Visual Composer now, along with our custom integration or Cornerstone. As stated previously, we will continue to provide patches to Visual Composer for stability and security; however, we encourage all customers to switch over to Cornerstone (especially for all new sites) as there are many exciting new options and features, with many more in development! Ultimately, the most important thing to us is stability for our users, and we apologize for any confusion that might have been caused by our previous communication.
We ran into some conflicts with third-party plugins using less than desireable CSS selectors that were colliding with our ravamped Font Awesome output system, so we've gone ahead and made a minor revision to how that is implemented. In the v4.0.0 notes we discussed this at length and the method of using
data attributes to output icons. Going forward, that
data attribute has been renamed to
data-x-icon to help avoid problems like this. The previous notes will be appended to reflect this as well. While this change originates from Cornerstone and the shortcode output for icons, many icons are implemented throughout the theme that take advantage of this output scheme, so we have updated numerous templates within the theme to reflect this alteration.
Things have been very exciting around Themeco HQ after the release of our new page builder, Cornerstone! We are hearing some truly fantastic feedback from our users and we are thrilled about continuing to build out new and exciting features so that we can ultimately make your page building experience in WordPress and X as fun and hassle-free as possible.
Speaking of hassle-free, we've included a Raw Content element into this release of Cornerstone to making writing custom content a little bit easier. While the Text element can work for certain pieces of content, there are situations in life when you just don't want WordPress auto-populating your content with empty
<p> tags. If that is the case, then the Raw Content element is for you! It's a pretty simple little element (and purposefully so). Any markup you output in this element will be wrapped in a
<div> with a class of
x-raw-content, which you can add additional classes or styles to if needed. One thing to note is that there is no spacing or styling applied to this element in an attempt to make it as "invisible" as possible. The Raw Content element accepts shortcodes and is the best way to output custom shortcodes in Cornerstone.
For this particular update, we are also shoring up a few things here and there throughout the plugin that were meant to be rolled into the initial release but got left out in the hustle and bustle of launching. Firstly, we had to make a minor change to the Font Awesome icon integration mentioned in the previous X release notes to avoid a few collisions we found with third-party plugins utilizing CSS selectors that weren't very modular. To get around this, we've namespaced the icon
data attribute so that it is now
data-x-icon, which should prevent any of these intersections from happening. The original notes (which go into great detail on this update) have been updated to reflect this change.
In the process of moving from X – Shortcodes to Cornerstone, a few of our previous shortcode names did not get mapped over correctly due to some minor typographical bugs on our part. These have been addressed and will function as they should moving forward. We've also included some minor fixes to make certain elements clickable in the preview area (e.g. map embeds) and ensure that output is mirrored on the frontend as it is in the preview area (e.g. responsive text).
We've also addressed a some minor issues relating to utilizing Cornerstone in various situations. For example, we fixed an SSL mixed content warning inside the editing interface, updated the WordPress editor control to receive images and shortcodes properly, and altered the load process for Cornerstone to help avoid potential conflicts with third-party plugins. The new load process will disable script minification and page caching when editing so content can display properly; however, this will not change anything for your frontend performance.
Again, we cannot stress enough how excited we are for the future of Cornerstone! It's may only be a couple days old, but we're looking forward to seeing it grow up and how it will make the editing experience in X much more streamlined.
Woohoo! v4.0.0 of X has finally arrived and it is without a doubt our biggest and most mind-bottling release to date (seriously...like, 1,000+ commits in a month)! We're incredibly excited to finally unveil what we've been feverishly working on and hope that you all get as much of a kick out of it as we do. That being said, the heart and soul of v4.0.0 actually doesn't have much to do with the theme itself. Instead, the biggest piece to this release comes in the form of a brand new plugin. Ladies and gentleman, meet Cornerstone.
Cornerstone is the result of many months of planning, numerous sleepless nights, copious amounts of caffeinated beverages, and one team meetup in Beantown, Massachusetts for a final hurrah. "Cool stuff," you say. "Neat logo," you exclaim. "But, what exactly is it?" you wonder. Without further ado, let's jump into some FAQs and get to the bottom of things!
With regards to the theme, not much actually. As far as plugin support is concerned, X is now updated to be compatible with the following versions of our integrated plugins:
The most significant update we've worked into the theme for this release is how we handle the output of Font Awesome icons. Instead of using CSS classes for each icon (e.g.
.x-icon-home), we're now using inline
data attributes to determine the output of each icon. Ultimately, this resulted in a stunning 20% reduction in stylesheet size, making things much cleaner. If you're simply using the
[icon] shortcode throughout your content, all of these changes will be implemented automatically behind the scenes.
There may be some instances where you have handwritten icons in your HTML to be used in special circumstances where shortcodes are not allowed (e.g. navigation links). If that is the case and you are updating from a previous version of X, an option will be turned on in Cornerstone's settings that enqueues a separate stylesheet with the old Font Awesome class names to ensure that nothing changes on your site. That being said, we strongly recommend that you update the markup of these handwritten icons to their new versions so that you can turn off this stylesheet and remove the extra HTTP request and extra CSS from your page.
Updating the markup of these icons is fairly simply. For example, let's say that you have an icon in your navigation that is outputting the home graphic. This might look something like the following based on previous versions of the shortcode's output:
Moving forward, the first thing you would need to do is find the unicode representation of this icon. To do that, you can simply go to Font Awesome's icon list and find the icon you want and click on it. For this example, we're looking for the home icon, which will ultimately take you to this page. Below the icon examples we see the unicode value for this icon is
f015. We can now take this value and update the markup like so:
<i class="x-icon-home" data-x-icon=""></i>
We keep the
x-icon-home class because the CSS now looks for any
class attribute that contains a class with a string of
x-icon- anywhere in the attribute. If it sees this string of characters, it will know you want to output an icon and will look to the
data-x-icon attribute for the content of this icon. This also allows us to quickly see that we intend for this to be a home icon, but the important part to remember here is that the label doesn't do anything here, just the
data-x-icon attribute, we can see that our unicode value of
f015 is prefixed by
&#x and suffixed by a
;. This is important so that the CSS knows how to work with this value properly. If these values are not present, the unicode string will be output instead of the intended icon and will appear broken.
Once you do this a few times, you will see that the update process is very simple and doesn't take long. When everything is in place, it's not something you will need to update often unless you want to change out the icon. Also, remember that this is only needed if you are handwriting icons in very specific situations, but as long as you are using the
[icon] shortcode in your output, this is all taken care of for you.
Speaking of shortcodes, all shortcode names are now prefixed in our new builder with x_ before them so that they are better namespaced. If you are using our provided shortcodes within X, the old shortcode names have been aliased over for backwards compatibility, but moving forward it would be a good idea to utilize the newer naming conventions and update any old markup accordingly. Using our previous example of the
[icon] shortcode, this would now be called
[x_icon]. This actually has more to do with the shortcode plugin, but we're mentioning it here since there are some updates regarding that with this release as well, which we will go into more detail on in a bit.
We've also made some small updates to various features throughout the theme, such as removing any predefined date formatting for page and post meta information. There were also a few bugs we've addressed such as dropdowns occasionally disappearing too quickly when hovered over as well as the megamenus not being contained properly within the navbar. Other than that and a few additional administrative changes on the backend, nothing too drastic has been altered in the way the theme functions.
The answer to all your hopes and dreams. In all seriousness, Cornerstone is a standalone plugin with a custom tailored, 100% frontend interface for building pages and posts with our personal and custom integrated shortcodes. It is meant to take the place of X – Shortcodes in our continuing efforts to streamline the creation process within X, making it as simple and efficient as possible. Similar to X – Shortcodes, it is required when using X.
If you have a moment, we've put together a little introductory walkthrough of the plugin below that is a great first look at Cornerstone! We plan on releasing more detailed videos on various aspects of Cornerstone in the coming weeks, but we cover a wide array of topics here that should be really helpful in getting a sense of what Cornerstone is and how it operates. Enjoy!
If you've used X before, you'll find the onboarding process to be the same as our other Extensions. Additionally, when utilizing Cornerstone alongside X, your validation of the theme will double as your Cornerstone validation (huzzah). If you're migrating to Cornerstone from X – Shortcodes in a preexisting WordPress installation, you can read about that process in greater detail here.
X – Shortcodes was thrown a lavish party, given a beautiful gold Rolex, and was never heard from again. In other words, it has retired (sad trombone).
Going forward, Cornerstone is the new kid on the block! The original purpose of X – Shortcodes was to store all plugin related functionality needed for X within a true WordPress plugin. Now that Cornerstone is being used, it will provide X with that same functionality and so much more. This preserves data portability and is consistent with WordPress standards. Once Cornerstone is installed and you are using X v4.0.0 or later, you can safely deactivate and delete X – Shortcodes.
Nothing. Old pages built with Visual Composer will continue to work, and you can continue to use VC if you wish. That being said, Cornerstone is an incredibly versatile and cutting edge tool that is 100% managed in-house here at Themeco, so we encourage customers to begin using Cornerstone on new sites and to transfer the old ones over if they wish and as they have time (again, VC will continue to work and be supported so you do not have to update anything if you don't want to). We will continue to patch Visual Composer and provide plugin updates when necessary; however, we will not be mapping in any new shortcodes or functionality.
We've included a new option on the X Integration tab of the Visual Composer settings page to completely turn off all custom integration when using X and let the plugin behave natively. Please note, doing this means that any existing pages you've currently built with Visual Composer in X might be affected greatly due to the fact that we overwrite Visual Composer's rows and columns.
They will continue to work just fine! We completely understand that this is a new option for our customers, which is precisely why so many options are given (yay)! That being said, we cannot stress enough that we encourage all users to take the time to migrate their pages from Visual Composer into Cornerstone if desired. This process can be done slowly over time (one page every now and then), all at once (in a mad dash to get in all that Cornerstone goodness), or not at all (womp womp). Ultimately, the choice is yours.
As you build new pages for your website, we strongly recommend that you begin using Cornerstone if you chose to use a builder as that will ultimately be the cleanest way to do anything in X, although you can certainly still insert shortcodes manually if desired. Alternately, if you feel you would like to continue using Visual Composer, that is still an option.
Regretfully, no. Due to the different styles of the two builders, they are not cross-compatible in any way. You can safely use them side by side (i.e. some pages built in Visual Composer while others are built in Cornerstone) but you can't edit a page built in Visual Composer with Cornerstone.
Ah, that little guy! He's still there, don't worry. The previous generator button labeled "X – Shortcodes" that appeared above the WordPress editor now features a solitary cornerstone that looks like and has no other label.
Great question! The best place as always is the Knowledge Base in the member center. We've added quite a few new articles covering different aspects of Cornerstone in detail:
We have a thread going in our forums to discuss Cornerstone. No support will be provided in that thread, just general feedback and discussion with our developers. It is expected when a new tool like this is released that there will be a lot of questions and potential issues. Be prepared for several updates these first couple weeks after release. We will also be launching a contest in a few weeks with regards to Cornerstone that has some fun rewards (cash and prizes), so be on the lookout for that once the dust settles from the launch.
We are so incredibly excited about v4.0.0 of X and Cornerstone. This is the beginning of an exciting new chapter in the Themeco world that will enable our users to more effectively take advantage of the tools available to them.
The Email Forms (MailChimp) plugin has been updated to v1.1.0 to make it compatible with v4.0.0 of X and our new release, Cornerstone. It is important that you only update to this version once you have updated to v4.0.0 of X and installed Cornerstone in your WordPress installation, otherwise you will experience some issues as this version utilizes new structural shortcodes available only in Cornerstone.
This release of X is a simple update to correct a non-critical issue that came to our attention after the previous update was released. When running WordPress v4.2 and saving settings in the Customizer, the save state of the Customizer button was not being set properly. As previously stated, this is not necessarily an update that needs to be implemented based on the situation at hand, and this fix will certainly be rolled into our coming release of the theme. Users who wish to wait for the next release of X are certainly safe to do so if they desire.
With v1.0.1 of the Email Forms (MailChimp) plugin, we issued a minor update to address a situation where shortcodes were not displayed on the Email Forms list table after updating to WordPress v4.2. This did not affect the output of any current shortcodes already created, and simply made them not visible in the list table.
We're very excited to announce our final release of X before v4.0 hits the ground running! This particular release is a maintenance update in response to v4.2 of WordPress about to come out, some minor security updates, as well as updating Revolution Slider to the most recent version available. Enjoy the release and we look forward to having v4.0 of X in your hands very soon!
This update to X focused primarily on improving user experience throughout the theme and doing a little tidying up where needed. One of the biggest improvements to this release has to do with providing more consistent checks in the WordPress admin area for some of our features such as the demo content installation and Customizer reset functionality. Because these features can alter settings if utilized, it is important to ensure that you receive one final prompt before confirming your decision. In response, we've included a flexible new modal interface that we can plug in where needed throughout the admin area. You can see a preview of what this will look like below:
confirm(), where before the action is completed, the user must affirm their previous decision. This keeps your data from being overwritten accidentally, and also gives a little bit more of a user friendly modal to interface with.
Beyond that, we've included support for the latest offerings of bbPress and WooCommerce, which included one minor update to our integrated WooCommerce templates (specifically the
cart-totals.php template). Other than that, everything else is good to go!
We've also improved the interaction with desktop dropdowns to ensure that they don't disappear as quickly if a user accidentally mouses off them. We have only received a few inquiries about this, but we wanted to go ahead and take a look at it to see if there was anything we could update to make it a little more user friendly, and this expanded interaction is a subtle but helpful addition.
#x-content-band-1) was present in the address bar but that element wasn't on the page. Our newly included check for this has made sure that this won't occur anymore.
On the PHP side of things, a very nuanced bug regarding background images was taken care of as well. Essentially, if a user's blog page was set as their front page and the most recent post added had a unique background image, that background image would show up on the blog page itself. We've included a small conditional statement to ensure that this is only output on single posts and pages to keep this from happening.
The X – Shortcodes plugin was retired on May 28, 2015 in favor of our new page builder plugin, Cornerstone. For more information on this transition, check out the X v4.0.0 release notes. Cheers!
Providing styling for MEJS's advanced controls was the main priority of this particular update to allow for greater consistency in how WordPress integrates with MEJS. Below are a couple examples of what this will look like for audio and video in Integrity:
As you can see, there are a few additional elements added to the audio and video players when these advanced controls are activated. Firstly, a current time and total time indicator are added to either end of the time rail on both players, giving users a little more feedback on the media they're playing. Additionally, both audio and video players receive a mute control, and the video player recieves a fullscreen control.
By default, WordPress' native
[video] shortcodes will utilize this advanced configuration as this is standard for their output; however, X's
[x_video_player] will allow users to access these controls if desired via the newly added
advanced_controls parameter. This provides greater flexibility for users to choose between a more streamlined interface and one that has a little more granularity to it.
Finally, we have included some minor shortcode styling updates throughout. These were implemented to improve structure, and pertain mostly to the MEJS updates.
This release of X was mostly a maintenance update centered around integration with other plugins and fine-tuning some elements throughout the theme. The main updates to this version of X are BuddyPress v2.2, additional WooCommerce updates for v2.3, some WPML compatibility alterations, and numerous smaller items throughout the theme.
Regarding BuddyPress v2.2 updates, we took time to go through every template included with the theme and have ensured that all is in order. The biggest update to this version is that the "Create a Group" button was moved from above the main header on that specific page into the main navigation for that section of BuddyPress (see below):
Other than that, everything else related to BuddyPress was mostly behind the scenes. We've also include a WPML compatibility update into this release, which actually fixes a minor issue on the plugin's end. We have contacted the staff at WPML and made them aware of this as our hope is we will not continue needing this fix in our theme. The fix relates to the language switcher dropdown in the main navigation and some native WordPress classes that the plugin is missing, which are needed for things to appear correctly. Until this is remedied in the plugin itself, we will keep our theme specific fix in place so that all is in order.
In addition to our minor maintenance items included throughout the theme (which you can read in more detail on the changelog), we've included a pairing notice between the theme and the shortcodes plugin. As you all know, the shortcodes plugin is required with X as much of the functionality the theme uses is placed into that plugin, and the plugin is necessary to conform to WordPress best standards. While it is sometimes okay to update either the theme or plugin and not the other, increasingly we want to stress the importance of always keeping these two items up to date and in sync with one another. In an effort to do this, if you have updated your theme but not the shortcodes plugin, a notice will appear instructing you to do so to keep everything in order. These notices will disappear once these versions are in sync with one another. We are hoping this will serve as an extra reminder to keep things up to date, which ultimately benefits everyone with the latest features and updates in performance.
Finally, we have made some modifications to our provided child theme based on recent updates to the WordPress Codex's child themes page. Due to poorer performance, instead of using
@import in the child theme's CSS file to import the parent theme CSS into the child theme, X now enqueues the parent theme's styles separately and then enqueues the child theme's stylesheet on top of that. There have been many articles written about how this affects performance and even with an additional HTTP request of two stylesheets instead of one, the removal of using
@import results in some fairly significant performance updates.
One of the biggest impacts this has on our child themes is that we no longer need to provide a child theme based on each Stack! You can simply use one child theme for all of your designs and not have to bother if you're using the correct one. Our newly updated child theme that we provide will have all of this setup for you already, but if you are interested in updating an old child theme of yours, simply update X and X - Shortcodes to the latest version (this will not work unless you are using v3.2.2 of X and v3.0.4 of X - Shortcodes or higher), remove the
@import statement from the style.css file in your child theme, and add the following snippet of code to your functions.php file in your child theme:
add_filter( 'x_enqueue_parent_stylesheet', '__return_true' );
This sets the
x_enqueue_parent_stylesheet filter to true, enqueuing the parent styles separately from being imported using
@import in the stylesheet itself. This ultimately makes management of your child themes much easier and keeps the stylesheet a little cleaner. You will also notice in our provided child theme that we've updated the
/framework/views/ directory to have all stack options available. You do not have to utilize this feature at all to override templates, but if you do need to override a template, simply make sure that you have it updated in the right place and you'll be good to go as always, but you don't need to worry about the other empty directories being there even if you're not using them as they won't affect anything.
We've included some minor performance improvements between the theme and shortcode plugin styles and made minor adjustments to some shortcode shortcode functionality. There wasn't anything in the way of a major overhaul this time around, just a little bit of good housekeeping!
With v1.0.1 of the Smooth Scroll plugin, we took some time to investigate a minor behavioral bug that was cropping up from time to time in different browsers, rendering text unselectable. Upon further investigation of this item, we discovered that the
touchbehavior property of the
.niceScroll() plugin appeared to be instigating this when set to
true. Altering the value of this property elminiated any instance of this behavior.
With this release of Under Construction we took some time to evaluate the markup output of the plugin itself to see if there was a way we could make things more efficient. When activated, the plugin will now overwrite page markup to non logged in users so that no content is present other than the notice. This also allowed us to ensure that the notice was rendered more consistently across mobile devices, creating a more seamless experience in utilizing the plugin.
White Label has been updated so that when a replacement logo is used on the WordPress login page it will now link out to your website's homepage instead of the default wordpress.org link. Additionally, the title attribute for this link has been altered to pull through your website's name specified in the WordPress settings.
This maintenance release was put out in response to an issue with a small segment of users who had ASP tags enabled by default in their hosting environment's PHP configuration files. This conflict led to the "Visual" editor not loading for this small segment of users, and was quickly remedied by updating our templating tags used for structuring the shortcode generator.
data-x-element="x_mejs" attribute was left off of the native
[video] shortcodes, leaving these shortcodes previously unstyled.
With our recent overhaul of the X Shortcodes, we implemented a new function in the plugin called
function_exists() call to ensure that the function is available before attempting to utilize it.
[slider] shortcode. Additional checks were added to ensure that the JSON data used is being properly utilized.
This update was a very minor update to ensure that the proper minified production files were being enqueued, rather than our unminified source files.
This release includes a little bit of everything from new features, to integration updates, optimizations, and more. To begin we'll start by saying that we've updated our integrations with WooCommerce, BuddyPress, and Visual Composer (you can find more information on the Visual Composer updates towards the bottom of the post)! X is now ready for the coming release of v2.3 of WooCommerce with updated templates, styling, and functionality. One important note is that WooCommerce v2.3 is currently nearing an "official" release but is still technically in "beta." If you are using WooCommerce on your website, it is recommended that you do one of two things:
It is important that you do one of the preceding actions if you're using WooCommerce, otherwise there could be potential conflicts with updated/outdated methods, styling, et cetera.
Additionally, BuddyPress has now been updated to support v2.1.1, which brings some exciting new features to the plugin, including support for the @mention functionality previously only available via an additional plugin. Check out the image below to see a preview of how this looks:
This works similar to Twitter in that if you want to reference another member in an update, you simply start with the "@" symbol and then begin typing. Even if you can't remember a username, this functionality will apply your search to both the username and the person's real name, making it very flexible. Once you see the user you'd like to add, simply select their name and it will be added to your post. This makes interacting with other users much more natural as this type of functionality is commonplace across most social networks.
Furthermore, we've swapped out our previous audio and video library for WordPress' native audio and video library, MediaElement.js, which allows for native browser support with Flash fallbacks when necessary. Switching over to MEJS ensures that we're keeping things as streamlined as possible within X, and it's also the first step in moving our background video feature for sliders and content bands towards this new library as well, which will ultimately make things more flexible and optimized across the board. Our implementation of MEJS into X is completely custom, ensuring that all styling and functionality is lean and quick, creating a great tailored experience.
Additionally, we've included numerous maintenance updates for items such as one page scrolling and dropdown support for when the "desktop" navigation is viewable on a mobile device such as a landscape tablet. We've also simplified some of our class names for various elements as well, so if you have styles applied to some of these, you will want to make sure and update them in your child themes. For example,
.x-container-fluid is now
.x-container throughout the theme. Additionally, we've done away with the
.x-responsive-video-shortcode classes, and simply given the outer video container a class of
.x-video, and the inner container class an updated name of
.x-video-inner. Because of this, now our video and audio shortcodes follow a similar output in class name and make it really easy to target what you're wanting to style. Here is a quick example of the class output for the container element of each media shortcode within X now:
That about covers everything regarding the theme, let's move onto the X – Shortcodes notes!
In an effort to continually improve our integrations with various plugins, a large part of this update takes place "under the hood" to ensure that various features of Visual Composer work as seamlessly as possible with X.
Secondly, we've put many options back into users' hands on what features they'd like to see in the plugin. If you now to to Settings > Visual Composer, you'll notice that there is a new X Integration tab available on this screen. By default this will have many elements turned off that we feel aren't necessary when utilizing Visual Composer with X due to duplicate functionality or unnecessary functionality, but should you desire to enable certain features again you can now do so here.
This release of X Shortcodes is our biggest update yet for a lot of reasons. We've put in a ton of work to ensure that our shortcodes are handled in a more friendly manner for the frontend editing feature of Visual Composer and we have also completely overhauled our shortcode generator! Let's start with the new shortcode generator.
First, you'll notice that the old TinyMCE button within the visual editor is gone in favor of a new button directly above the editor:
This was done to ensure that the shortcode generator is always available, whether you prefer to use the visual or text tab of the editor. Upon clicking that button, you'll be met with a familiar looking modal setup that feels right at home in the WordPress admin:
To the left you'll find the modal navigation, which is broken down by the same sections that have been present in previous versions of our shortcode generator, as well as our Visual Composer integration. Beneath each section is a list of shortcodes pertaining to that classification, which when selected will bring up the options for that shortcode:
This interface allows you to simply scroll down through the list of options available for any given shortcode and select what you'd like them to be. Once you're done, simply click Insert Shortcode down in the lower right corner and it will be output to the editor wherever your cursor was. Keep this in mind as you'll need to make sure the cursor is in the right location when you're trying to nest shortcodes such as content within a content band or an accordion item within an accordion.
Additionally, you can use the advanced control toggle in the upper right portion of the header to turn on or off the advanced CSS controls for various elements. Essentially, this should display an ID, class, and style input that will allow you to assign a unique ID, class, or inline styling to your element should you desire. If you don't ever plan on using these, it might be best to toggle these off to keep things as clean as possible. Whatever you have selected will be remembered as you use the modal going forward. Below is a screenshot of the toggle when it's active (take note that it has turned green and a couple extra controls have appeared near the bottom named "Class" and "Style;" some elements such as the Content Band don't have an ID input since it's ID is generated dynamically):
In addition to the new shortcode generator, we've also included a new parameter to the
[content_band] shortcode entitled
marginless_columns. when set to
true, this parameter will change the way that the columns inside the band operate (specifically, it will remove the spacing between them and ensure that all columns are of an equal height until they go fullwidth on mobile devices). The best way to get the most mileage out of this new feature is typically to employ it with a similar amount of padding across each column within the band and to give them some sort of background color to see the effect. Below is an example of what this might look like:
To achieve this look, you might use a piece of code that looks something like this:
[content_band class="center-text" padding_top="0" padding_bottom="0" no_margin="true" marginless_columns="true"] [column style="padding: 35px; background-color: #ff9900;" type="1/3"] … [/column] [column style="padding: 35px; background-color: #ff480f;" type="1/3"] … [/column] [column style="padding: 35px; background-color: #2e9eff;" type="1/3"] … [/column] [/content_band]
Probably the most easily overlooked part of this effect but definitely one of the more important pieces is that the height of all of these columns is the same. This type of layout does not happen naturally in web design, but through some clever CSS and one additional parameter, we're able to make this possible. This opens up whole new doors of design possibilities when you stack numerous layers. For example, try a background image on the content band with columns that have varying degrees of opacity on their background color. The options are truly limitless once you dig in! Keep in mind for this fullwidth effect we're using a page template with no container and we have no inner container on our content band, which is what allows everything to stretch the entire width of the site. Also, be mindful of the content you place within your marginless columns, as you don't want to crowd it with too much information.
Due to switching out our previous audio and video player with WordPress' native library, MEJS (MediaElement.js) in v3.2.0 of X, some modifications needed to be made to Video Lock to ensure that everything worked as it should. Essentially, a check was included to ensure that the MEJS library is always loaded when Video Lock is used on a specified page.
In v3.1.0 of X we updated the bundled version of Visual Composer to v4.3.5. One of the major differences between this version of Visual Composer and the version previously bundled with X was the addition of new hooks by the plugin that themes are required to hook into for certain features to be setup properly. Because of this, updating the theme first could potentially cause an update error as there is a momentary "gap" during this in-between period where the hook does not exist. Because of this, we have included a fix in this release of theme to get around this, but you may still encounter an issue based on various circumstances in your installation. If you are having a problem updating Visual Composer, please go through the following steps:
If the update still does not work, deactivating it first might help as well. If these methods do not seem to be working for you, you can locate the plugin .zip file itself within the theme at
/x/framework/plugins/js_composer.zip and install that manually via the WordPress admin panel (i.e. Plugins > Add New > Upload Plugin).
Nothing significant was updated in this release other than a few additional minor plugin structure updates. It was mostly put out to keep everything in sync via automatic updates for our customers.
This update included a lot of maintenance work as well as some major overhauls and updates to various parts of the theme that we feel have provided some great improvements to how certain processes are handled. Most notably would be our changes in consolidating some settings in the Customizer for efficiency, the navigation (which now features new mobile styling that is more friendly to navigate on smaller devices and updated one page navigation functionality), a new one click demo content installer, right to left style updates, and a more optimized image generation system. Without further ado, lets dive right in!
As previously mentioned, one of the biggest changes to this update is our consolidation of some repeated controls into a more centralized location in the Customizer. Upon updating and going into the Customizer for the first time, you should see the new Layout and Design section like so (this is an image of it expanded):
You should notice that the options located within this section are similar to some of the first groupings of options previously available in the specific Stack sections. We have moved these options here in an effort to consolidate repeated items and make working with data in the Customizer more efficient. Your old options will be ported over to these new settings once you login to the admin area for the first time after updating, so you shouldn't have to change anything around or worry about anything breaking.
As far as mobile navigation is concerned, dropdowns are now hidden by default, making for a much more engaging and easier to consume user experience. They are toggleable via the arrows on the right hand side of the menu item, which will slide to reveal the items beneath. This was a huge navigation overhaul and we feel it has brought a new level of ease to the theme that your users are sure to appreciate! Below is an example of what this might look like:
Furthermore, we've improved upon how the "one page" navigation features work so that this functionality is more universally accessible no matter where your reference links are coming from. For example, you can now add links to sections on your page from content links such as a button, which will trigger the page scroll if desired. You can also link to a section of your one page site from another page (such as a blog post) and have the offset calculated and accounted for cross-page, which makes things much smoother for users.
We've also included a new Demo Content section under Addons in the WordPress admin area, which allows users to setup example content based on our online demos with the click of a mouse! We know that for a long time many of our users have wanted a more automated process for this part of working with the theme and we are pleased to finally bring this exciting new feature to everyone. The interface is incredibly simple to navigate and utilize:
Essentially, you can choose which demo you would like the importer to be based off of from our online demos by making a selection from the first dropdown. This will import the homepage content and Customizer settings for that installation to your local installation. For the homepage markup, you can select between our standard shortcodes or a Visual Composer compatible form. Please note, while no pages or posts you currently have will be altered in any way with the demo content, importing the demo content onto your website will overwrite your Customizer settings as previously mentioned. If you already have your site setup but are curious to try out this feature, please make sure that you first backup your Customizer Settings by going to the "Customizer Manager" tab under "Addons" and making a backup of your settings.
Additionally, you can choose to import some demo posts and portfolio items should you desire. Doing so will setup some examples that showcase how to utilize the various features utilized for each post format or portfolio item type. The great thing about the importer is that it keeps things clean and doesn't mindlessly import posts and pages over and over. It will only import what you ask for, and if it is already present it will not duplicate anything. Menus are automatically setup as well for easy linking out to these new pages. For online demos with a blog page as the homepage, this will be setup accordingly.
As previously stated, we're incredibly excited about this new feature and we feel it will assist all of our users greatly in learning more about X and how to utilize various features. For more detailed information about the demo content importer, you can go here.
Also, this release saw a big overhaul of our right to left styles including massive improvements to the header styling and shortcodes throughout. If you use X in a right to left capacity, we hope you enjoy!
And finally, we've also greatly improved our image generation systems after consolidating our options in the Customizer for the various Stacks. Since we used to have site dimension options located within each Stack's set of options, we would have to calculate and generate images to be used for all Stacks in case a user happened to switch back and forth. Consolidating our options in the Customizer has allowed us to reduce our number of required images by 75% down to only 4, making things in your uploads folder much more lightweight. As always, if you have changed your site's dimensions or have changed your Stack, it is a good idea to run the Force Regenerate Thumbnails plugin to ensure that your image dimensions are being calculated correctly.
On top of those major updates, we've also included numerous optimizations and maintenance fixes to the theme as well as updating the integrated version of Revolution Slider to v4.6.5 and the integrated version of Visual Composer v4.3.5 along with WordPress v4.1 support!
Our shortcodes plugin has received some updates regarding the output of various elements such as the column as well as some updated styling and functionality. Definitely make sure that you update both the theme and plugin together to ensure that everything is on an equal playing field and that nothing is missing in terms of compatible styling or functionality.
Potential Layout Issues – As noted above, we have updated some of the column styling, navigation styling, et cetera in this update to make things a little more efficient. If you have any sort of browser cache or site caching setup for your installation, your layout may appear to be "broken" or certain features might not seem to work (such as dropdowns) as the old cached version is still being output while the new markup is present. To get around this, ensure that both the theme and shortcode plugin are updated and clear your browser cache as well as any caching that might be setup on your site via a caching plugin. This will ensure that both the proper markup and styling are being output to your installation and everything will be in order.
In this release, we took some time to address a few minor items to improve upon our recent v3.0.0 update of X. Those items include:
In this release, we took some time to address a few minor items to improve upon our recent v3.0.0 update of X. Those items include:
We are incredibly excited to bring you all our biggest release to X yet: v3.0.0 is finally here! With v3.0.0 of X, we're forging ahead with a completely new paradigm and focus to product development—Extensions. For a brief overview of what each Extension entails, make sure to check out our Extension demos.
For more detailed information on Extensions, make sure to check out our Knowledge Base article, which covers everything seen here as well as some extra information. It will be updated to reflect any changes we make to the Extensions process going forward. Without further ado, lets continue on learning about Extensions!
The great thing about these Extensions is that they keep the theme free of additional size or features that not every user will necessarily find useful or needed. They also allow us to take certain features to a new level (such as email integration), that wouldn't be as efficient or functional placing into the theme directly. Extensions for X are broken down into two categories:
Themeco developed Extensions are plugins developed exclusively by our team and built to be used seamlessly with X, which require X as a base to operate. Third party developed Extensions are plugins developed by outside developers that we have either integrated into our theme or partnered with to bring to our users based on the functionality provided. As of v3.0.0, our Themeco developed extensions include the following (with a short description of each):
Additionally, our third party developed Extensions include the following (with a short description of each):
All Extensions (Themeco and third party) are managed via the new Extensions submenu item under the Addons menu.
While third party plugins will have their own settings menu dictated by the plugin developers, any activated Themeco Extension will have its settings page appear beneath the Extensions submenu item like so:
This allows for one central location to manage all Themeco Extensions quickly and easily. To add new a new Extension, simply go to the Extensions page, which looks like the following:
You will notice that Slider Revolution and Visual Composer are available to install immediately. These plugins have always been available with X as a bundled plugin and do not require product validation to unlock. All Themeco developed Extensions and Soliloquy are made available after the theme has been validated. For more information on this process if you have not done it already, please consult this Knowledge Base article.
Upon successfully validating your purchase, previously "locked" items will become available for download:
After installing an Extension, if it is activated or deactivated its status will be reflected via the badge below the name:
Selecting the Manage Plugin button will simply take you to the Plugins page for you to activate or deactivate the plugin as needed.
We are incredibly excited to bring these incredible new features and functionality to our users in this release for X. We look forward to having our users take advantage of these new Extensions and seeing what they do with them "in the wild."
This release of this shortcodes plugin contained some minor stylistic updates to various shortcodes, so definitely make sure you have that in place so everything is up to date.
Check out the video below as it contains a brief overview of the changes made in both v2.6.0 of X and v2.5.0 of X – Shortcodes.
Check out the video below as it contains a brief overview of the changes made in both v2.6.0 of X and v2.5.0 of X – Shortcodes.
This version of X is being put out in response to a bug that was brought to our attention with v2.5.0 that kept plugins from being downloaded or read about via the Plugins menu in the WordPress admin area. We have looked into this and found the issue that was keeping this from working properly and it has been remedied. This is a minor update, but an important one for this functionality to work correctly. For all of the main information about the X v2.5.0 and X – Shortcodes v2.4.0 update, please make sure that you check out our previous release notes to read up on product validation, automatic updates, and everything else introduced in that version of X.
Who doesn't like the simplicity and ease of automatic updates? Whether you're working on a single personal site, or managing a complex network of websites, automatic updates help make everything run a bit more smoothly. With v2.5.0 of X, we've built out a completely custom automatic update API for X and its associated products (e.g. X – Shortcodes, and more to come in the future)! Without further ado, let's jump right in and see how it works.
Please note, this feature is only available starting from v2.5.0 of. Upgrading to X v2.5.0 is required to make this available for your current site and for future updates. You may download your latest X theme form your ThemeForest download page and then all future updates can be done automatically if you have followed the necessary steps outlined below. You must still update to version v2.5.0 manually.
For a detailed run-through on how this new system works and how to setup your WordPress installation to start receiving automatic updates, definitely check out this article in the Knowledge Base as it goes into detail on this process. For the purpose of these release notes, here is a quick rundown of everything (again, make sure to check out the article referenced above for a more detailed description):
That's pretty much it! As mentioned before, the system built out here in our member center and the theme will start serving up even more exclusive goodness in the future for our members who take advantage of this feature, so don't delay.
All of this functionality is included under the new Addons section, which you'll find directly under the Dashboard link in the WordPress admin area. This Addons section is where we will include any functionality that is unique to X. In the future, the first time you activate X you will be redirected to the Addons Home page, which will provide you with information on how to register and setup product validation, along with quicklinks to helpful resources here in the member center. Once you have validated your product, the initial prompt to register will go away to clean things up a bit.
Next, we have the Custoimzer Manager section under Addons. This is the new home for the Customizer import, export, and reset functionality. These used to reside under the Tools menu in the WordPress admin area, but have now been moved here in an effort to better consolidate our X-specific functionality.
Finally, there is the Product Validation page, which is used to enter in your API key that is generated here in the member center. Again, check out this article to learn more about this entire process in full detail.
In addition to the new Themeco API that handles automatic updates and future exclusive products along with the Addons section, we've also updated the necessary templates to ensure that X is compatible with v2.2.0 of the WooCommerce plugin.
Regarding icons throughout the theme, we've made a dedicated switch to Font Awesome from Foundation Social everywhere in the theme, with the exception of the
[social] shortcode for right now. We initially used these two different icon sets as Font Awesome did not used to support the breadth of social networks that it now does. With this increased pool of options to choose from, we can now easily make the switch over to one dedicated system, which also improves the overall look and consistency of things. Please note, Foundation Social and the
[social] shortcode will be deprecated after two more release cycles and will no longer be functional at that point. We are leaving them in for the time being so that our users can switch out shortcodes if needed to a Font Awesome equivalent. All other areas of the theme such as the topbar and footer social links, the share links in the portfolio, et cetera, have all been swapped out automatically within the theme.
We have also completely removed the Google Authorship Markup from the theme as Google has put an end to this program. Your Google+ profile under your user account will still be pulled through in appropriate places such as the
[author] shortcode, but it will no longer trigger the extra markup needed for Google Authorship.
Along with everything else listed above, we have also done various maintenance updates to the theme to ensure that everything is working in tip-top shape!
The newest version of the X – Shortcodes plugin sees the addition of a shiny, new shortcode! The
[counter] shortcode can be used to add an interactive element to your pages that will increment to a predefined number as you scroll down the page. This number can be prefixed or suffixed with text or symbols, and text can also be placed above or below the numbers to provide additional descriptions. This type of shortcode is great for sharing stats or quick blurbs of information about your company or product, and is a great way to engage users as they make their way down your pages. Be sure to check out our shortcode demos to see it in action!
Additionally, we've gone through and updated the few Bootstrap related scripts we utilize to v3.2.0, ensuring that everything regarding tooltips, popovers, and more is as up to date as possible. This update has addressed a bug that made the tooltips and popovers "flicker" at times if moving over a link too fast.
You asked for it and we're incredibly excited to announce that it's finally here: X officially offers integrated bbPress styling and support with the latest release of the theme! This has been a long requested feature from some of our users and we couldn't be more thrilled to finally release it out into the wild. Without further ado, let's dive a little deeper into the X bbPress integration.
bbPress is a very cool plugin that allows users setup forums on their WordPress installation. It offers up a host of functionality to suit your needs and also integrates seamlessly with BuddyPress if you happen to be using that as well (which we added support for in our previous release)!
There are a lot of considerations to take into account when structuring and styling the various elements utilized throughout the plugin. Add in the fact that X is not only responsive, but features numerous options to alter site width, content width, et cetera, and things can get very tricky very fast. However, we really wanted to take some time to properly assess all that bbPress had to offer and do our best to modernize it in a fresh and stylish way. We started with what we had done with our BuddyPress integration and built off of that to make the two plugins work seamlessly together. If you're using bbPress on it's own, it will look and function great. If you happen to be using it with BuddyPress, the two will look and function as one seamless user experience unlike anything ever seen before with these two plugins!
Similar to our BuddyPress integration, we have also included an optional navigation item that can be activated via the Customizer. Upon enabling this in the Customizer, this item will automatically populate a list of links for you that are bbPress specific. It also is dynamic based on whether or not BuddyPress is activated on your site. For example, if BuddyPress is not active, a profile link will be present, but if BuddyPress is active and the BuddyPress navigation item is active, this link will go away as the BuddyPress link already serves this purpose. Everything is laid out and structured intelligently so that there is no overlap and items are only utilized when needed.
The biggest thing to glean from all of this is that no stone was left unturned in this integration. We really took time to go over every detail with a fine-toothed comb to ensure that things not only looked great, but performed great as well. This meant implementing some markup updates to the bbPress template files to ensure that elements were targeted as uniformly as possible. Additionally, like our other plugin integrations, styling for bbPress is only loaded if bbPress is active and will not affect performance for users who aren't taking advantage of the plugin. And with regards to the styling for bbPress, we managed to style the entirety of the plugin in only 13K of CSS, a very small amount considering the great deal of complexity that bbPress offers up.
Please note, we will only be supporting the versions of bbPress that are listed in the member center (more detailed information on this can be found in the bbPress Integrated Plugin article in the Knowledge Base). We will make sure to be constantly testing new versions of bbPress when they come out as part of our release cycle. At the time of this writing, the only supported version of bbPress with X is v2.5.4. Additionally, there are several new and updated Knowledge Base articles related to bbPress, BuddyPress, how to setup galleries, and using transparent colors.
Along with all the bbPress goodness that comes with this release, we've done some maintenance and optimization to the theme that have cut down on some CSS.
This update of the shortcode plugin includes updated styling for certain elements, like alerts with bbPress, et cetera. Make sure that you update to this version along with the new version of the theme to ensure that everything is in order.
You asked for it and we're incredibly excited to announce that it's finally here: X officially offers integrated BuddyPress styling and support with the latest release of the theme! This has been a long requested feature from some of our users and we couldn't be more thrilled to finally release it out into the wild. Without further ado, let's dive a little deeper into the X BuddyPress integration.
BuddyPress is a very cool plugin that allows users setup a social network of sorts on their WordPress installation. It offers up a host of functionality that can be enabled/disabled to suit your needs such as extended user profiles, friend connections, private messaging, activity streams (think Twitter feed), notifications, user groups, and more! As you can imagine, all of this functionality means that BuddyPress is a beast of a plugin to work with and integrate (not a scary beast, more of a noble, majestic beast).
Those are a lot of considerations to take into account when structuring and styling the various elements utilized throughout the plugin. Add in the fact that X is not only responsive, but features numerous options to alter site width, content width, et cetera, and things can get very tricky very fast. However, we really wanted to take some time to properly assess all that BuddyPress had to offer and do our best to modernize it in a fresh and stylish way. After days of workshopping and wire-framing various ideas we ended up with a simple, elegant, and engaging approach to building out a community on your website.
One of the biggest challenges we faced when working with BuddyPress was how to address all of the navigation on various pages. Practically every page features a top-level navigation and a sub-navigation that can oftentimes include numerous links. Figuring out the best way to handle all of this data in a simple, streamlined manner was a difficult task, but we've come up with a great way to manage it all in a clean, responsive fashion. Below are some screenshots of how this would look and function on a user profile page:
Another area that took a lot of time to think through properly was the activity streams on the site and how those modules would be represented. Ultimately, we worked through a simple, classic styling that worked great for handling these particular modules:
Private messaging has also been optimized for readability and ease of use:
We have also included an optional navigation item that can be activated via the Customizer, similar to how the navbar search feature is activated. Upon enabling this in the Customizer, this item will automatically populate a list of links for you that are BuddyPress specific based on the settings you've implemented in the plugin. For example, if you don't want to have user groups implemented as a part of your website, then leaving that option deselected in the WordPress admin will ensure that a link to the groups directory doesn't show up. It will also dynamically populate registration and activation links if your site is open to public signups, and it will show a login link for signed out users and a profile link for logged in users. Below is a screenshot of what this menu might look like depending on your settings on the site.
We could go on and on as there are literally dozens and dozens of pages, sub-pages, directories, et cetera with BuddyPress, but the biggest thing to glean from all of this is that no stone was left unturned in this integration. We really took time to go over every detail with a fine-toothed comb to ensure that things not only looked great, but performed great as well. This meant implementing some fairly extensive markup updates to the BuddyPress template files to ensure that elements were targeted as uniformly as possible. Out of the box BuddyPress has quite a few inconsistencies with how they apply class names and markup various elements, so a lot of our work entailed refactoring this from the ground up for greater consistency. Additionally, like our other plugin integrations, styling for BuddyPress is only loaded if BuddyPress is active and will not affect performance for users who aren't taking advantage of the plugin. And with regards to the styling for BuddyPress, we managed to style the entirety of the plugin in only 22K of CSS, a very small amount considering the great deal of complexity that BuddyPress offers up.
Along with the extensive BuddyPress updates outlined above, we also took some time to prepare X for the coming changes in WordPress' v4.0 release. One of the biggest ones here is the moving of the Customizer and Customizer import/export functionality. In WordPress v4.0, some new updates have been made with how the Customizer link functions, so instead of using our custom admin menu item like we had before, we've moved it back under the Appearance menu, which is where it normally is in a stock WordPress installation. This ultimately provides greater consistency across themes, ensuring that users are comfortable finding the Customizer link where it should be:
Because we had to move the Customizer link back to the Appearance menu, this also meant that we needed to find a new home for the import/export functionality of the Customizer (along with our new reset feature). To keep things nice and clean (as we like to do around here), we placed these features in the Tools section of the WordPress admin menu. Once you click on the Tools link, you will see the following boxes:
Here you can easily import and export your Customizer settings just as you have always done with the added benefit of everything being on one page. Additionally, as noted above we've added a new Reset box in this space that will allow you to delete all of your Customizer settings, essentially making everything start over from scratch as noted in the box.
Also, we've revamped the way that widgets are registered within X so that our users can now take advantage of widget management via the Customizer. Previously, we used to dynamically register/deregister widget areas based on settings in the Customizer. We have changed this so that all header and footer widget areas are registered at all times, but the ones that are not active will be given a "disabled" styling in the admin area to indicate that they are not able to be used:
If you are still using WordPress v3.9.X, you should see all of your widget areas available to you at the bottom of all the sections listed out in the Customizer. If you happen to be using a public beta of WordPress v4.0, you will notice a section at the top of your Customizer sections labeled Widgets. This is a Panel, and it is a new Customizer API control given to developers allowing them to group together similar components in the Customizer. At this time, it appears that panels cannot be moved beneath normal Customizer sections, but we are waiting to see if this will be changed in the public release of v4.0.
We've also included numerous updates to the way that styles and scripts are enqueued throughout the WordPress admin area to ensure that they're only loaded when needed.
A few minor bugs that were brought to our attention with the last release have been fixed, including Flash videos not loading properly in Firefox and rounded/circle images not having their proper styling applied. There were updated almost immediately and fixes were provided in the forum if users needed them, but they are now being released into production. We have also included Revolution Slider v4.5.95 with this latest release of X.
This update of the shortcode plugin included one minor fix that was calling an option from the Theme Modifications API instead of the Options API, which was switched out in v2.2.0 of X. This has been accounted for and is all good to go now.
It's no secret that performance is a big deal to us around here at Themeco. We believe there is always something we can be doing just a little better in order to make X perform more effectively. The core of this release was centered around some very big and important performance updates with regards to the Customizer, that coincidentally have improved frontend performance as well.
Essentially, WordPress has two methods available for storing options in the database. Through many long nights of research and investigation, we found that the method we were using with the theme seemed to be somehow related to the load times of the Customizer. We'll skip all of the technical tedium here, but the results we found were pretty definitive as switching from one method to the other saw incredible performance improvements with X.
On the backend in the Custoimzer, the time it used to take to load the page HTML averaged around 3.36s with the page load event firing around 6s (remember that there is a lot of data loaded into the Customizer to handle all of the functionality carried out there). Switching out option methods saw that HTML load drop to around 0.638s with the page load event firing around 2.4s. This means that on average we were seeing an 81% decrease in HTML display and 60% decrease in the time it takes for the page load event to fire. Similarly, on the frontend we saw HTML display times drop from 1.02s to 0.703s on a test page with a significant amount of self-hosted content and third-party content, resulting in a 31% decrease here as well.
Ultimately, the most important thing to take away from all of this is that you should notice enhanced performance both in the Customizer and on the frontend of your website by updating to v2.2.0 of the theme. Do keep in mind that this update utilizes a new method for storing and retrieving options as mentioned above. Please note, we have implemented an automated update script that should take care of the switch for you the first time you login to your admin panel after updating the theme, so make sure that you do that to ensure that everything is switched over properly (you should already be in the admin panel anyway if you're updating, so as soon as you're redirected back the script should run for you without any problem). Even though we've switched methods for utilizing options in WordPress, your old XCS files should still work if you absolutely need to use them, so you can try making a backup of all settings before updating even though everything should be moved over automatically as specified above. We'll be working to update the XCS files available in the Demo Content section as well.
Additionally, we've included quite a additional improvements and maintenance updates as well. All of this information can be found in more detail in the changelog, so definitely make sure to check that out if you'd like to see a list of everything else we worked on.
The shortcode plugin includes some minor stylistic updates to the image shortcodes, which were also a part of a fix that we implemented for some issues with Firefox regarding how it handled the styling of some of these elements.
The biggest addition to this release is the inclusion of a new option to activate navbar search. We're very excited to bring this new feature to the table as we know that many of you have wanted to see it in the theme for quite some time now. This new option can be found under the Header section of the Custoimzer. Once that section is open, you can find the new option under the Search sub-headline with one option labeled Enable Navbar Search. Selecting this option will place a new item at the end of the navbar, which will activate the search overlay when selected.
Additionally, we've begun the inclusion of various action hooks throughout the theme in an effort to further improve the extensibility of the theme. These hooks will be used for various developmental items going forward in an effort to streamline numerous processes throughout the development of the theme. We will be adding documentation on these hooks in the Knowledge Base very soon so that our users begin taking advantage of them as soon as possible.
Finally, we've done some extensive research into various performance items regarding both the backend and the frontend of the theme. In doing so we've managed to uncover some very important data points about how to improve plenty of aspects of the theme and have already implemented some changes in this version of the theme in order to prepare for these changes going forward.
The only updates to the shortcode plugin at this time were some minor stylistic updates to some shortcodes and some simple functional updates.
This release of X was geared entirely around addressing various bugs and improvements. Most of these updates were fairly minor and simply a matter of polishing up certain elements or the way that a function was handled throughout the theme.
The one notable exception to this is an update we made to the sidebar generator in the theme regarding how these new widget areas are created within the system. Previously, we were using an incremental numerical ID to keep track of sidebars as they were added to the system. Due to the way these sidebars were generated, this would occasionally create issues when old sidebars were deleted as it affected the numbering of further sidebars. To remedy this issue, moving forward we've begun using the Name of each sidebar as part of the sidebar's unique ID. This will ensure that no more sidebars will be lost through the deletion/creation process. Keep in mind that due to the fact that the sidebar's name is now used as part of a unique identifier, each sidebar created must have a unique name. It is highly likely that the vast majority of our users are already doing this, but we wanted to make sure to convey this in an effort to clarify matters.
Additionally, we've addressed a bug regarding bbPress index pages not displaying properly. Through our investigation this appears to be due to a strange quirk within bbPress itself. We have included the default bbpress.php files throughout the theme to bypass the standard output used in an effort to display the bbPress content properly. It should be noted that while these files are present, bbPress is not yet supported in X. We wanted to address this issue to ensure that core functionality was working as expected throughout the theme, but no further styling or support was added at this time.
This release of X – Shortcodes plugin was geared entirely around addressing various bugs and improvements. Specifically, we worked to remedy a few issues regarding the
[accordion_item] shortcodes as well as tooltips related to the
[image] shortcode. Basically just putting a little polish on a few small items in the plugin.
This release of X sees the addition of our first new Stack since launching at the beginning of the year: Ethos! Ethos is a content-driven, information oriented design that works great for websites where news is the central focus. We've included many exciting and beautiful features in this Stack that are unique to this design only, so make sure that you take some time to go through the new Ethos Customizer article in the Knowledge Base as it will walk through these in detail for you.
We've made countless performance enhancements, theme improvements, updates, and bug fixes with this release. They're too numerous to list here (over 2800 commits in our version control log), but we wanted to take some time to outline the biggest ones.
Script loading is one area that we have done a lot of testing with to see which ways of handling all that data work best. With v1.0.0 of X we would do some querying of the content for pages and posts and dynamically load scripts when needed (i.e. if the
[lightbox] shortcode was present, load the lightbox script). While on this surface this method appears to be better by only loading what you need when you need it, the fact of the matter was there were still many other scripts (mostly very small) that needed to be used all of the time. All of these scripts ultimately add up to more HTTP requests from the server, which is best to reduce as much as possible. With v2.0.0, we've made the move to minify and concatenate all theme scripts into two main files, one that enqueues all scripts that need to be in the
<head> element and another that enqueues all scripts that can be loaded near the closing
</body> tag. A couple other libraries have been left separate and are loaded dynamically when needed as mentioned earlier, but ultimately we reduced over 20 files down to 2, greatly improving response times in this area. Also, this means that all of your scripts are minified right out of the gate, so there's no need to worry about altering this via a plugin like W3 Total Cache, which can typically lead to issues if you're not familiar with how to utilize these features.
Similarly, we decided to make the move to minify all styles output by the theme as well and doing so saw as much as a 25% reduction in overall CSS size with certain files. Similarly to the scripts mentioned above, this also means that all CSS files for X are minified for you without any need to worry about this with an extra plugin on your site that can create issues when running these commands on your files. As always, any changes that you would like to make to the theme can easily be made in our child theme and you can now be assured that your CSS is being loaded as efficiently as possible on your website.
Another big feature of this release is the addition of megamenus! We know that many of our users have been asking for this feature for quite some time, and we're very excited to finally be able to bring it to you all with v2.0.0. If you haven't had a chance to do so yet, definitely take some time to run through the new megamenu article in the Knowledge Base as it goes into great detail on how to setup your menus and how you can expect this functionality to operate. Megamenus work across all Stacks and each one features their own unique set of styling.
As mentioned before, we've included countless additional updates and bug fixes that have greatly streamlined the way many processes are handled with the theme. Many of these have more to do with the backend, but they've gone a long way to improve upon the foundation we've already put forth with X. We look forward to seeing what you all create with Ethos!
The latest release of the plugin features some bug fixes and minor backend updates.
We'll try to keep these release notes short and sweet as this update is simple maintenance release to address some minor bugs and improve performance, structure, et cetera when possible throughout the theme. Additionally, we've also readied a few things for our next big release, which will be v2.0.0 and feature our highly anticipated 4th Stack, Ethos! We've very excited about v2.0.0 and look forward to seeing what everyone does with it once it's available.
In the most recent version of the theme, one of the biggest bugs we've tackled is displaying sliders on the blog index page. As it has been noted throughout the forum, blog index pages would not display sliders if they were assigned to the page due to the way WordPress operates and handles these sections of your site based on settings in the WordPress admin area. Effectively, WordPress no longer views the blog page as a "Page" in the sense of it being a "Page" post type in the system. Technical details aside, we've managed to implement a fix that addresses this developmental nuance and now gives you complete freedom in outputting your sliders on these sections of your site if needed.
We also included numerous updates with regards to different pieces of functionality, most notably the one page navigation. We've updated the way this script works so that all offset calculations are set properly even on longer pages with lots of content, which can prove to be an issue on slower connections, lesser hosting plans, et cetera.
Along with these feature and performance improvements there have also been numerous small updates made to the frontend and backend of the theme to aid in performance, output, and troubleshooting moving forward. Ultimately, things have been made a little more streamlined and performant, which will help ready things for the v2.0.0 release of X as well.
Additionally, we've updated Visual Composer to v4.1.3 with this release of X. We happened to notice a bug with this release of Visual Composer where the duplication button was not working for the shortcodes. After a short time investigating this we discovered a bug implemented by the Visual Composer team and worked to remedy it on our end. The important thing to take away from this is that the bundled version of Visual Composer that comes with X will have this bug fix in place, but if you have your own license for Visual Composer and download v4.1.3 on your own, this bug will persist. To ensure that you're using the latest version with the bug fix that we implemented in Visual Composer ourselves, please follow the plugin update instructions in the Knowledge Base.
We made one major update in the plugin itself and the way that the parallax backgrounds are calculated. Previously, if bandwidth was slow or a page had lots of content this could result in erroneous offset calculations for the background images. We have implemented a fix that addresses this issue and should ensure that all parallax backgrounds are output properly.
As described in the previous release notes we had to overhaul the file structure of the X – Shortcodes plugin to accommodate our new automatic update feature as well as the latest round of Visual Composer updates. In doing this, we spent so much time testing these new features it went unnoticed that the shortcode generator button had gone missing from the TinyMCE interface. We have released this quick fix to addresses this issue and you should be notified of it in the WordPress admin panel, which will prompt you to update the plugin automatically if you have v2.2.0 installed already.
The main purpose of this release is to ensure as much as possible that everything with our third party plugins are up to date and accounted for as much as possible. We understand that the recent string of Visual Composer updates have been problematic and want you to know that we've done everything we can to address these matters on the theme side of things (which isn't much, but we've at least tried to help troubleshoot these plugin issues as much as possible). Through our assistance on these issues, we have found that for the most part the v188.8.131.52 patch that was released by Visual Composer some days ago seems to have fixed most of the issues that were being caused in conjunction with WordPress v3.9. Visual Composer has just released v4.1.2 of their plugin and we have bundled that with this newest version of the theme.
v4.1.2 of Visual Composer is being described as a "WP 3.9 Compatibility Update," and we are hoping that it fully address all of the issues that have been brought up by our users who are using Visual Composer along with WordPress v3.9 (even though v184.108.40.206 seems to have taken care of a majority of matters). The following list is taken directly from Visual Composer's changelog and outlines the updates made to this version of the plugin:
vc_add_param()and other helpers api functions are back to normal.
On top of bundling this newest release of Visual Composer with the theme, we've also made some additions to the theme regarding the updating of third party plugins bundled with the theme (i.e. Visual Composer and Revolution Slider) in an effort to make this process easier for everyone. Going forward, once you have updated your theme to the newest version from ThemeForest, you should be notified to update these plugins from within the admin area. These notifications will appear as a prompt at the top of your WordPress admin area as well as the update badges that appear next to the Dashboard > Updates and Plugins links in your admin area. Once these update prompts become visible you will be able to automatically update your plugins with the newly bundled plugins included with the most recent version of the theme that you've upgraded to.
One thing to note about this new feature is that as we began incorporating it into the theme we actually happened to come across a bug in the WordPress core related to this automatic update process. This isn't anything to worry about as it won't interfere with your automatic updates, but if you happen to have debug mode turned on while WordPress is updating a particular transient, you might happen to see a warning message while attempting to update these bundled plugins. This occurs because the update system uses the
WP_Cron system to update a transient called
update_plugins. When WordPress is performing this update the error appears, otherwise it uses the cached version in the transient and happily continues on. We've actually opened up a Trac ticket that you can read through if you'd like to understand this situation in a little more detail. The main thing to take away from this is that it will not interfere with your third party plugin updates and these messages will only appear under a very specific set of circumstances. We simply wanted to make sure that we notified everyone of this for the sake of the small group that might actually encounter this warning to give them an idea of why it's happening and know that this is not a theme problem but related to a bug in the WordPress core.
We have plans to include this automatic update feature for the theme in the future as well, but it is a more extensive update and will require some time to work through all of the necessary features for this bit of functionality. At this time, updating your theme will follow the exact same process as outlined in the Updating Your Theme and Plugins article in the Knowledge Base.
This latest update of the shortcode plugin also includes an automatic update feature, which is independent of how the updates for Visual Composer and Revolution Slider mentioned above operate. What this means is that if we ever push out an update to the shortcode plugin before pushing out a new update to the theme, you will be notified of this in the WordPress admin area and be able to update the plugin at that time if desired. For the most part, we tend to bundle new releases of the shortcode plugin with the theme but this ultimately provides us with more flexibility in getting features or fixes out to you all faster if we need to.
This is exclusively a maintenance release in response to the simultaneous updates of WordPress to v3.9, Visual Composer to v4.1, et cetera. This release does not have any additional features, but does include some important patches that are necessary to work with the latest versions of WordPress, Visual Composer, et cetera.
Because of some major changes with how WordPress handles the TinyMCE functionality in v3.9, this led to a couple issues with our shortcode plugin, as well as Visual Composer, Revolution Slider, and pretty much about any theme or plugin provider as there was not much time from the beta release to the public release to check into things along with the other projects we had on our schedule at the time. Regretfully, these "perfect storms" happen at times and we certainly apologize for any inconveniences that this situation might have caused you. We have been working tirelessly since the first reports came in of some of these issues to release a patch to everyone and we're pleased to announce that it is now here.
With this release we've updated Revolution Slider to the most recent version (v4.3.6) and Visual Composer to the most recent version (v4.1) along with including some fixes to our own shortcode plugin and the theme itself regarding Visual Composer integration. Visual Composer released some new features that were causing issues with saving background colors, images, et cetera on the
[content_band] shortcode, as well as some other quirky things here and there. Unfortunately, these updates and new features for Visual Composer were not readily outlined in their developer documentation or knowledge base, so we had to take some time to dig through the files ourselves and find what elements needed updating. Fortunately, it ended up not being too extensive, allowing us to get this patch out quickly.
Some of our users have reported further issues using Visual Composer v4.1 with WordPress versions below v3.9. It is strongly recommended that if you update Visual Composer to v4.1 that you also ensure you have X, the X – Shortcodes plugin, and your WordPress installation all updated to their latest versions. The X – Shortcodes plugin is backwards compatible with older versions of WordPress, but utilizing legacy WordPress software with the newest Visual Composer plugin could present some problems, so keep that in mind when updating. As a best practice, it is always a good idea to ensure that everything is up to date when a new release is made available. Should you have any questions on how to perform these operations, don't forget to check out our Knowledge Base as it features an extensive writeup on how to properly update your theme and plugins.
The major update implemented in this version of the theme is the ability to choose between different layouts for the logo and navigation. We know that many of you have wanted this ability for some time now, so we're very happy to finally make it a reality!
The options for this setting can be found under the Header section of the Custoimzer beneath the sub-section labeled Logo and Navigation. The first setting you'll notice is the Layout, which provides you with Inline and Stacked options. Selecting the inline layout will keep everything as it has always been (i.e. logo and navigation both contained within the navbar), whereas selecting the stacked layout will place the logo in a separate container above the navigation and they will both be centered. Below is an image of the Inline layout option:
Below is an image of the Stacked layout option:
When the Stacked layout option is selected, two additional settings will appear below entitled Logobar Top Spacing (px) and Logobar Bottom Spacing (px). Altering the values of these inputs will allow you to set the spacing above and below the logo in the logobar when it is visible, giving you the ability to align your logo exactly as you'd like.
It should be noted that these options will still be visible even if you have Fixed Left or Fixed Right selected for your Navbar Position because if you activate the one page navigation feature on a particular page, you these settings will be applied to that page. On top of this feature, we've also included some general bug fixes and maintenance updates to the theme as well.
In this update of the plugin we've added a new
author_id parameter to the
[author] shortcode, which will allow you to display the information for another author other than the author of a particular page. If nothing is entered in for this parameter then the author of the page will be used instead. To find the ID for a particular author that you're wanting to display, simply go to Users in the WordPress admin panel and click on the profile page of the user that you're wanting to output. Once you've done that, look at the URL bar in your browser and you should see something like this:
Take note of the
user_id parameter in the URL, which is where you will be able to find the ID for the user. In this particular instance the ID for this user is
12. So, if you wanted to output the author information for this user you would need to write out your shortcode like so:
Finally, we've updated the output of the author's name so that instead of defaulting to the Nickname in the user profile, it will instead output whatever is selected for the Display name publicly as select input. This ultimately provides you with a greater deal of flexibility in terms of how this information is output.
This update was mostly geared towards the WordPress backend and some considerable improvements we've made towards your experience with the Customizer specifically. The Customizer in and of itself has been completely overhauled in an effort to start start introducing true "live preview" capabilities as you make changes to your theme with certain settings.
By default, the Customizer works to show you a preview of your settings by going through a few different steps (broken down a bit for the sake of brevity):
<iframe>is removed, leaving only the newest version.
We'll be rolling out more additions to these "live preview" settings in the coming weeks as we release new features with the theme. While it isn't possible to have every feature function as a true "live preview" setting (i.e. Stack selection), we are going to work our hardest to switch over as much as we can to the new system as quickly as possible. At the time of this release, the following options are what has switched over to the new system:
:hoverstyles will be able to be included with these methods going forward for the reasons previously mentioned. Fortunately, this shouldn't be a huge concern as you wouldn't be able to see the
:hoverstyles instantly anyway due to the fact that it they require a cursor to activate them.
Beyond the Customizer updates with this release, we've also included the latest version of Revolution Slider (v4.3.3) and Visual Composer (v4.0.4). It should be noted that we have implemented all of the necessary changes to accommodate the newest offerings from the Visual Composer plugin, but much to our chagrin have had to disable the frontend editing ability at this time due to a few developmental nuances of the plugin itself. We spent a considerable amount of time investigating how other other theme providers are dealing with these same realities and they all seem to fall into one of three camps: they're still not using v4.0+, they are using v4.0+ but have disabled the frontend editor, or they are using v4.0+ but have bugs with how the frontend editor operates with theme integration. Because we wanted to get the ball rolling on this update, we've gone ahead and worked on everything we can at this point and are personally working with the Visual Composer team to address the various bugs we've found while working with the frontend editor. As soon as these issues can be addressed by their team, we will be quick to add back in the frontend editing capabilities as soon as possible.
Finally, we've included some general bug fixes and maintenance to the theme. One of the more notable ones is that we've updated how the Disable Page Title meta option works while using Renew. Before, disabling the page title simply removed the title from the header area of Renew, but many of our users noted that they felt the entire header area should be removed as this is what they expected. After receiving some additional feedback on this, we decided to update this feature to reflect these expected behaviors. Now, selecting Disable Page Title when using Renew will completely remove this header region, affording a greater deal of flexibility when working with pages.
With this edition of the X – Shortcodes plugin, we've added an offset attribute to the
[recent_posts] shortcode, which affords users the ability to specify an initial offset for which post shows as the first post of the shortcode. This gives users a lot of flexibility in terms of stacking multiple
[recent_posts] shortcodes together to achieve higher post count displays or unique mixing and matching layouts. Take some time to go through the new sections of the
[recent_posts] shortcode demonstration page to see only a small sample of what is possible with this new option. This is also the initial groundwork of some bigger updates we have planned for this shortcode in terms of offering even more flexibility (displaying excerpts, displaying sortable portfolios, et cetera). Stay tuned for those updates as we're excited to bring them to you in the coming weeks!
We are very excited to bring multiple portfolio support to the latest version of X! This is pretty much the bulk of the update for this version as the implementation was quite extensive and greatly changed the way that portfolios used to function in the theme. That being said, let's begin by walking through this greatly requested new feature in the theme so that you can get everything up and running in no time!
Adding a portfolio to your theme is no longer a manual process of linking out to the archive page automatically generated by WordPress. Instead, we have replaced this functionality with a new page template found under the Page Attributes meta box in the sidebar that can be selected using the Template dropdown (see image below). The name of this new template is Layout – Portfolio, and selecting this is the first step in setting everything up.
Once you have selected the Layout – Portfoio template from the dropdown, a new meta box will appear somewhere below your editor labeled, Portfolio Settings. It is in this meta box where you will manage most of the settings pertaining to the portfolio you are setting up for this page.
Once you have set all of these options for your portfolio, you're good to go! One additional thing to note is a new setting on each of your portfolio items in the Portfolio Item Settings meta box called Portfolio Parent. This setting is a simply dropdown list that keeps track of how many pages you have assigned the Layout – Portfolio template to. By default, all of your portfolio items will choose the first item in this list as the portfolio parent. As you add more portfolios to your site, this list will continue to grow, and you will want to make sure to filter these items appropriately. Whichever parent portfolio page you choose for your portfolio items is what will be linked to for things such as your breadcrumbs, et cetera, so it's very important that you setup all of your items according to how you'd like them to behave. If you're only going to be using one portfolio on your site, you can leave this set to Default and you won't have to make any more edits after that.
Finally, the last thing you'll need to make sure you do is set your Portfolio Slug in the Customizer to something different than the slug your base portfolio page is set to. For example, if you have your portfolio setup at
mydomain.com/my-portfolio/, then do not use
my-portfolio as the slug in the Customizer. Instead, use something like
my-portfolio-item in this field. This is a reality of working with multiple portfolios via a page template in that this slug must be set as a global across all of your portfolio items, and it must not match any of your portfolio index pages. Keep this in mind if you have multiple portfolios as well. Let's say you have two portfolios setup at
mydomain.com/my-second-portfolio/, if your portfolio slug in the Customizer is set to
my-portfolio-item then all portfolio items will be listed out as
mydomain.com/my-portfolio-item/title/ when you click through to them regardless of which portfolio is their "parent." Simply remember that your slug will be used across all posts no matter how many portfolios you setup on your site.
Nothing major was changed in this version of the shortcode plugin other than some minor updates to the way that certain shortcodes function. The most notable fix included an update to the LinkedIn sharing link in the
[share] shortcode that would ultimately result in an error if a page or post was too long. Updating to this version is not mandatory if you update your theme, so you do not have to worry about it if you aren't using any of the features mentioned above.
Finally, we've also updated Revolution Slider to v4.2.5 with this release of the theme, so if you're wanting to make sure that you have that version setup, head on over to the Knowledge Base and follow the instructions laid out in the article about keeping your theme and plugins up to date.
With the latest release of X, WooCommerce v2.1+ is now supported. When WooThemes released their v2.1 update to the plugin recently, a lot of things changed throughout the plugin from the ground up. Our updates to the theme were quite extensive to fully support all of the new features and functionality altered in the plugin, so if you've been waiting to update your WooCommerce plugin to the latest version you can now do so safely. There isn't much to relay regarding this particular implementation other than the fact that there is a lot of work that needed to go into things under the hood to support this latest version, so we're glad that we can finally bring this to our customers as we know many of you have been eagerly anticipating it.
Additionally, we're very excited to bring right to left language support to all Stacks within X! Setting up your WordPress installation for right to left text will automatically load a small selection of additional styles to reposition elements accordingly and ensure that everything works well for this configuration. Again, there is not a lot of specific information to share about this update as it is more of a behind the scenes update for users who will take advantage of this.
Finally, we've included some additional bug fixes, maintenance updates, and optimizations across the theme. One of the biggest performance updates made to this release is the compression of the CSS output to the
<head> of the theme based on selections made in the Customizer. We were able to reduce the size of this CSS by over 35%, and as always we will continue to seek out ways that we can improve on various aspects of the theme.
This update includes a complete overhaul of the Sidebar Generator in the theme, which now allows you to set unique sidebars on your blog index, portfolio index, shop index, and any taxonomy page throughout your site (i.e. tags, categories, et cetera)! If you haven't taken advantage of the Sidebar Generator yet in X, you're missing out! You can locate it at Appearance > Sidebars in your WordPress admin panel. Below is a screenshot of what the new interface looks like:
We know that many of you have been asking about this feature for quite some time and we are very pleased to finally be able to release this update as we know it will help you to more easily achieve your desired layouts with X. We truly hope that you enjoy this exciting new release!
Another big update with this theme has to do with slider management. Up until now, we've included all of our slider options in the Customizer under the Sliders section. While this was a very cool way to manage slider placement in X, upon investigating this further we found a couple issues utilizing this method:
Taking this into account, we determined that the best way forward was to completely remove the Sliders section from the Customizer and move these options to custom meta boxes on the Pages edit screen. You will now find these options split up into two meta boxes below the editor for your Pages. These meta boxes are labeled Slider Settings: Above Masthead and Slider Settings: Below Masthead. By default these meta boxes are collapsed, but expand to show all of their options once you select a slider for your page. Below is an image showing the collapsed state of the meta box:
And the following image shows an example of the meta box expanded after selecting a slider:
All of the options are the exact same as they were in the Customizer other than the fact that there is no option for slider position anymore (i.e. above or below the masthead). Instead, simply utilize the correct meta box depending on which location you want your slider to show up in. Please note, any sliders you have already set via the Customizer will need to be reset with these new meta boxes. Migrating your settings from the Customizer to these meta boxes shouldn't take too long as there are only a small grouping of options for each.
Beyond that, we've included a couple minor bug fixes and updates to the themes regarding styling for some shortcodes as well as improved Gravity Forms formatting.
This version of the plugin is a simple one and mostly consists of migrating certain scripts from the theme to the plugin as mentioned above. Beyond that, we fixed a small bug keeping the
[visiblity] example from being output to the editor screen when using the shortcode generator.
The biggest part of this release that we're pleased to bring everyone is styling support for Gravity Forms! We've gone through and tidied things up to ensure that your forms look great with X and that they are completely responsive as well. The styles for Gravity Forms are conditionally loaded only on pages that feature a the
[gravityform] shortcode, leaving other pages unaffected by the additional styling data. This will ensure that visitors coming to your homepage or browsing your site aren't met with any extra styles that they don't need. We know this is something that many users have asked about since our first release day and we're pleased to finally bring it to you.
Additionally, we've included a new section of options in the Customizer under the Blog section. There is a new Archive sub-section, which allows you to set layout and style options for your archive pages (categories, tags, date, et cetera), similarly to your blog. What this means is that you can now setup all of your category and tag archives like "mini-blogs" if you'd like, since some users like to break out their posts into different categories like "Blog," "News," et cetera.
Also, you can update the titles (and subtitles if present such as with Integrity) of these archive pages by going to the edit pages for your various taxonomies. For example, if you had a News category for your posts and wanted to change the title that shows up on the archive page for this category, all you would need to do is go to Posts > Categories, then locate the category you want to edit and click on it. Once you are on the edit screen, you will see two new options labeled Archive Title and Archive Subtitle. If you leave these empty, the default title will show on these pages, but filling them out will result in the titles being switched out accordingly.
If you want to link out to these category archives, you can do so by going to Appearance > Menus and selecting from the Categories menu to add links to your navigation and you're all set to go!
Regarding URLs as well, we've improved the URL rewriting of portfolio categories and tags. Whatever you have set as your URL slug for the portfolio in the Custoimzer will now also update portfolio category and tag archives as well. For example, if your slug was
my-work before, the category and tag archives for the portfolio were still
portfolio-tag respectively. Now, they would be updated to reflect
my-work-tag instead. Definitely make sure to update your permalinks if you're using the portfolio to ensure that these new URLs are working as expected for your site.
Beyond that, we've included various bug fixes and general maintenance tweaks to this release based on feedback shared with us from various customers. We greatly appreciate you bringing these things to our attention if you notice them as it allows us to ensure that X continues to improve as we move forward. That about covers everything for the theme, onto the shortcodes plugin!
With this release, we've added some new parameters to various shortcodes to improve upon their functionality, as well as fixing one bug related to the
[related_posts] shortcode. We'll outline these new features below
[recent_posts]– we addressed a bug that was brought to our attention that kept the filtering of portfolio posts by category. This has been addressed and the shortcode now functions as expected.
[skill_bar]– we've added a new attribute called
bar_text, which can be used to replace the percentage text that is seen inside the skill bar as you scroll down the page. Leaving this blank will default to the percentage.
[button]– we've added the
lightbox_thumbattributes to this shortcode, similarly to what we did for the
[image]shortcode in our previous release. This means that buttons can now be used to launch lightbox elements as well. Detailed information on how to utilize and implement the lightbox can be found here, which shows you how to take full advantage of the features offered with this shortcode.
That about covers everything for this week. Next week we're planning on producing and releasing some screencasts to walk users through how to utilize various shortcodes, setup pages, and more! Keep your eyes peeled for these resources as we think that they'll be a huge help for users who would like some more detailed documentation on how to take full advantage of these features.
As far as the theme concerned, we made a big discovery earlier this week with regards to the Customizer and its performance related to memory usage. We've had a very small number of users occasionally report issues with the Customizer stating that they were seeing a blank screen or an error message notifying them that they had run out of memory. This has most often been due to shared hosting plans, which were timing out because of this. We have been able to provide some solutions to help resolve this issue for this small group of affected users, but until recently had not figured out the source of the problem itself. After weeks of researching this in an effort to ensure that your experience with X is as seamless as possible, we have finally come to a resolution on this particular matter.
Through a few optimizations in regards to how we register and utilize options in the Customizer, we were able to dramatically decrease the amount of queries taking place on the database, resulting in a greatly diminished memory load. We will still keep our Knowledge Base article in place just in case someone still happens to have an issue with the Customizer, but we're happy to report that this issue has effectively been solved and should not occur anymore.
This version of the X Shortcodes plugin was geared to specifically target lightbox functionality. These improvements include caption support, video support, as well as an improved lightbox setup method.
[image] shortcode now has a new class that is added to the link that surrounds it when you use the
link="true" attribute. For example, If you were to enter the following code (simplified for demonstration purposes):
[image src="img.jpg" link="true" href="img.jpg"]
It would output some markup like this (again, simplified for demonstration purposes):
<a class="x-img x-img-link" href="img.jpg"><img src="img.jpg"></a>
x-img-link class is what can now be used as an automatic selector to setup your lightbox without having to do anything else. So instead of needing to add your own custom classes to all of your links around your images as well as setting up the proper selector with your
[lightbox] shortcode, this is all done automatically. You can still specify custom classes and selectors if you want, but you don't have to to get everything setup. Implementing a lightbox gallery could be something as simple as the following:
[image src="img-1.jpg" link="true" href="img-1.jpg"] [image src="img-2.jpg" link="true" href="img-2.jpg"] [image src="img-3.jpg" link="true" href="img-3.jpg"] [image src="img-4.jpg" link="true" href="img-4.jpg"] [lightbox]
This will automatically pick up the
x-img-link classes set to your images and will use the default options to create your lightbox upon clicking one of those images.
Additionally, we've added support for video and captions with the
lightbox_caption attributes on the
[image] shortcode. If you wanted to setup some images that launched a YouTube video on click, it would look something like this:
[image src="img-1.jpg" link="true" href="//www.youtube.com/embed/WxfZkMm3wcg" lightbox_video="true"] [image src="img-2.jpg" link="true" href="//www.youtube.com/embed/WxfZkMm3wcg" lightbox_video="true"] [image src="img-3.jpg" link="true" href="//www.youtube.com/embed/WxfZkMm3wcg" lightbox_video="true"] [image src="img-4.jpg" link="true" href="//www.youtube.com/embed/WxfZkMm3wcg" lightbox_video="true"] [lightbox]
So if you're linking out to a video on your image, simply set the
lightbox_video="true" attribute and you're good to go!
Also, you can add unique captions to your images now using the
lightbox_caption attribute. Using it would look something like this:
[image src="img-1.jpg" link="true" href="img-1.jpg" lightbox_caption="I am a caption!"] [image src="img-2.jpg" link="true" href="img-2.jpg"] [image src="img-3.jpg" link="true" href="img-3.jpg"] [image src="img-4.jpg" link="true" href="img-4.jpg" lightbox_caption="I am another caption!"] [lightbox]
Finally, you can specify unique thumbnail for the thumbnail navigation of the lightbox by specifying the
lightbox_thumb attribute. This comes in handy if you're linking out to a video and need to set a different image than what people will initially see. If this attribute is left blank or not used at all, this will default to whatever is set for the
src attribute. Using it would look something like this:
[image src="img-1.jpg" link="true" href="//www.youtube.com/embed/WxfZkMm3wcg" lightbox_video="true" lightbox_thumb="img-2.jpg"] [image src="img-3.jpg" link="true" href="//www.youtube.com/embed/WxfZkMm3wcg" lightbox_video="true" lightbox_thumb="img-4.jpg"] [lightbox]
We hope you'll find these enhancements and modifications useful as you build out your website. We cannot thank you enough for your continued support and look forward improving upon the foundation we've laid with X.
This latest version of the theme was more of a behind the scenes update, but it's a very important one for anybody choosing to use Visual Composer with the theme. As stated early last week, our new Visual Composer homepage templates are available in the Demo Content area for you to download and use immediately. We have provided information on some of the nuances of using Visual Composer with X, so you can take some time to read up on all of that if you'd like to get a better understanding of this release.
A couple little things to keep in mind when using the Visual Composer homepage templates are the following:
[vc_row]shortcodes). Instead, it uses the unique ID for that media item. Because of this, even though we have put placeholder images in place for all attributes, some of them might not show up, such as background images for the
[vc_row]shortcodes. Simply ensure that you edit each row and add in your own images and they will show up just fine on your site.
< >) don't get converted to HTML encoding, which will cause errors.
If you don't feel like digging deep and doing a little reading, the truncated version of all of this is that you will no longer have to perform any modifications yourself if you want to use one of our homepage examples with Visual Composer. This update took us the better part of last week to work on as it included some modifications to how our integration with Visual Composer works, as well as simply taking the time to create 30 new demo files from scratch. We hope that you will all find this to be an invaluable resource moving forward in saving you time getting your projects off the ground. As you all know, it is very important to us that we listen you each and every one of you and what you want out of X, which is why we have responded with this release.
In addition, we've included some minor bug fixes, LinkedIn sharing in the portfolio, a Behance social icon to the topbar and footer, as well as adding comment support on all pages, which was another request that multiple users had submitted to us. Upon updating to v1.7.1 of X, you may find that your old pages are now displaying a comments section at the bottom. To disable this, simply go into each of your pages and make sure that the Discussion meta box is turned on, and then deselect Allow comments and Allow trackbacks and pingbacks on this page. For those of you who don't mind being a little more technical, you can disable comments for all of your pages in one fell swoop by opening phpMyAdmin on your server, switching to the wp_posts table of your database, selecting SQL in the upper navigation, and entering the following query:
UPDATE 'wp_posts' SET 'comment_status' = 'closed', 'ping_status' = 'closed' WHERE 'post_type' = 'page'
Of course, if you have a different prefix for your WordPress database, your posts table might have a slightly different name, but you can still use this command as long as you enter in the appropriate table name.
We added a good amount of new attributes to our shortcodes in response to some requests that our users had mentioned. Here's a list of everything we've included.
titleattribute was added, allowing you to customize the title of this element. If no title is entered, it defaults to About the Author.
titleattribute was added, allowing you to customize the title of this element. If no title is entered, it defaults to Share this Post.
trueactivates a LinkedIn sharing link.
columnsattribute was added, which allows you to set columns for your
[toc_item]elements when the
blocktype is being used. Acceptable values are
categoryattribute was added, allowing users to filter their posts by category slug. Multiple categories are also acceptible when separated by a comma. We have some more plans in store for this shortcode coming up, as well as other shortcodes that will allow you to easily pull through content to your site, so stay tuned for that!
class attribute for the
[button] shortcode now gets added to the containing element when
circle is set to
true to provide greater stylistic flexibility.
This release features a big addition that everyone has been wanting for some time now: masonry blog layouts! You'll now be able to choose between a standard or masonry blog style, as well as select to display or hide your sidebar on the blog. When the masonry layout is selected, you'll have a choice between two or three columns, giving you a little flexibility in this area depending on your other settings for your site. Additionally, we've included the option to disable/enable post meta information, as well as alter the excerpt length.
Another huge update to this version is that we've added one page functionality to all pages in X. The option that used to be in the Customizer has now been replaced by a dropdown in the Page Settings meta box below the editor on each individual page. Simply create a custom menu in Appearnce > Menus and then set it using the dropdown mentioned before and you're good to go! Users who are utilizing the one page navigation feature from v1.6.0 will need to make sure to set this dropdown when upgrading as the old option in the Customizer is now gone and will not do anything once you upgrade. You can now easily create as many beautiful product pages, alternate home pages, marketing layouts, and landing pages that you want!
We've also made some improvements and additions to the Customizer. For example, you can now set an individual custom font for the navbar, whereas before this font was the same as your body font. Additionally, we've implemented a new section in the customizer called Site Icons where you can manage your favicon (desktops), touch icon (iOS and Android), and tile icon (Windows 8 Metro).
There have also been adjustments made to the markup of the theme so that all required elements for Google Authorship are in place to avoid any penalties your site might incur for them not being present.
As part of this update, We had to make some minor adjustments to the Site Layout option in the Customizer. Because of this, upon upgrading to v1.7.0 you will need to make sure to open the Customizer, select the appropriate option for this setting based on what you had in place before, and save your options. You will also need to make sure that you go through and set all of the new options available to you, such as the navbar font, blog style, post meta display, and more. We apologize for any inconvenience this might cause you, but there was truly no way around it for this update. We always make an effort to keep these things from having to take place, but in this particular instance it was unavoidable.
The only update made to the X Shortcodes plugin was a minor markup change with the
[recent_posts] shortcode in relation to our masonry update. Due to the addition of the masonry blog layout, a new
<div> with a class of
entry-wrap had to be added to the Renew and Icon posts to achieve the styling we wanted. Because of this, we also needed to ensure that it was added to this shortcode. This does not affect the usage of the shortcode itself.
The new year is almost upon us and as a little gift to you all we present our latest release of X, v1.6.0. This release sees the addition of one big feature requested by our users a lot over the past week or so, which effectively doubles the functionality of X. "What is it?" you may find yourself asking. Without further ado, here we go!
The biggest update to X is the addition of one page site navigation. Now, you can easily create a one page site with X using native WordPress features. To do this, you'll find a new setting under the Header section of the Customizer. This option will only become visible if you select Fixed Top as your Navbar Position. Upon doing so, you will see a new sub heading appear directly below labeled One Page Functionality. Beneath this sub heading is one option, and that is to Enable One Page Home Menu. Selecting this checkbox will add a new menu under Appearance > Menus > Manage Locations. The name of this new menu area is called Primary Menu (Home).
The menu that you place here can still accept normal links, but it can also accept ID links that correspond to elements on your page. Clicking these links will create a smooth page transition to that section of the page, allowing you to take advantage of this one page functionality.
Linking to these sections is incredibly easy. The IDs that you will use for your links can either be added manually to elements on your page (if you are writing your own custom HTML markup, e.g.
<div id="about">), added via shortcodes (most of our shortcodes accept an
id attribute), or if you are using the
[content_band] shortcode (the "Rows" in Visual Composer), each of these will automatically output a unique ID for you.
For example, say that you have three "Rows" on your homepage, if you were to look at the markup of these elements in your browser, it would look something like this:
<div id="x-content-band-1"> ...content here... </div> <div id="x-content-band-2"> ...content here... </div> <div id="x-content-band-3"> ...content here... </div>
These rows will auto increment, so if you were to add a new "Row" between your first and second row, the IDs would automatically update for you, like so:
<div id="x-content-band-1"> ...content here... </div> <div id="x-content-band-2"> ...content here... </div> <div id="x-content-band-3"> ...content here... </div> <div id="x-content-band-4"> ...content here... </div>
This is an important piece of information to keep in mind as you setup your links.
To setup the links to these sections on your page, simply go to Appearance > Menus and select the Links tab. This will allow you to place custom links into your navigation other than your pages or posts. In keeping with the example above, if I wanted to link to my second row, I would place the following value in the URL field:
Then give it a label (Link Text), select Add to Menu and you're good to go! The "active" state of these links will not become visible until you scroll down to the corresponding band. If you want one of these links to be active upon page load (usually the first one), simply select Screen Options in the upper right corner of the Menus screen, then select CSS Classes. This will add a new input field to your links when you expand them labeled CSS Classes (optional). In this field, enter current-menu-item if you want your link to be active on page load.
Keep in mind you can still add perfectly functional links to other pages on your site, and dropdowns too. Remember that this type of functionality works great for specific applications, but may not be fore everybody. It's also important to keep in mind that your homepage will have a different navigation than the rest of your site, so make sure that you plan out your site's information well.
We've also made some minor performance improvements with script and style enqueueing, as well as updating our Modernizr script to v2.7.1 with a custom build, which cut the file size nearly in half, so you'll get some extra gains there as well.
There was also one new option added to the Integrity stack under Portfolio Options that allows you to update the button text of the Sort Portfolio button that you see on the portfolio index page.
Finally, we have updated all language files included in the theme to reflect our new changes throughout.
This version of the X Shortcodes plugin saw a very minor update to the name used to call the thumbnail for the
[recent_posts] shortcode. Other than that, everything is exactly the same.
Please don't hesitate to let us know if you have any questions on how to use this one page feature. We're very excited to bring it to you all as we know it's something that you've been requesting for some time now.
From all of us here at Themeco,
Happy New Year!
This release was a quick fix to address a warning that was displaying if certain plugins were not installed while using Visual Composer.
The following items have been addressed in this release of X:
<body>element is now available on all posts, pages, and portfolio items. This can be found in the settings meta box for the respective post type you are using.
template-blank-8.phprespectively in the root theme folder.
.pofiles in v1.5.1 of X and have reprocessed the files to reflect new changes throughout the theme.
<head>as it was not needed due to our native styling.
With this release of X – Shortcodes, we have improved the performance of the
[vc_row] shortcode by cleaning up the way they are handled in the plugin.
This release of the X – Shortcodes plugin was a quick fix to simply swap the use of the
wpautop() filters on the
[text_output] content to ensure that certain content is not incorrectly removed.
After many hours of looking into the recent issues reported regarding Visual Composer, we have found that this particular situation has to do with v3.7.2 of Visual Composer and v3.8 of WordPress working together. The latest changelog for Visual Composer states that v3.7.3 included "Small WordPress 3.8 adjustments."" In our tests, it was only after updating Visual Composer itself that everything began functioning as it should.
We have altered nothing related to our Visual Composer integration code in the theme. At this time we do not believe it to be the source of the problem with this issue.
Since this issue was unrelated to our theme integration code, we were able to address this issue by updating the plugin itself. v1.5.1 of X features no changes in the coding of X whatsoever, merely an update to the Visual Composer plugin included within X. Thus, simply updating the theme will not resolve this particular issue as you must make sure that the latest version of Visual Composer is installed (v3.7.3). Once you have done that, everything will be in order regarding this particular conflict.
We wanted to take a minute to update you all about the latest release of X. Since our last notice went out, it has come to our attention that there have been some issues upgrading the theme.
All ThemeForest users can find the latest release of the theme available for download on ThemeForest. Unfortunately, there appears to have been an error in processing our latest batch of uploaded files as our single installable version of the theme did not make it up to the server. The packaged version of the theme with all files (documentation, demo content, et cetera) was updated while the single installable version of the theme was not. We have worked to address this and are hoping to have the single installable version of the theme available for download very soon.
For the time being, please follow the steps below to ensure that you are using the most recent version of the theme:
x.zipfile that contains v1.5.0 of the theme.
.zipfile you downloaded earlier.
Additionally, if you do not follow these steps exactly and find that Visual Composer or the v2.0.0 of the X – Shortcodes plugin isn't available in your WordPress installation, you can locate these files in
/x/framework/plugins/. You can use these
.zip files to manually upload these plugins if needed.
Regarding the X – Shortcodes plugin, in addition to completely revamping the visual interface, we had to modify three shortcodes in order to make them work with our Visual Composer integration. The three shortcodes that were modified are
[map]– This shortcode no longer takes an
<iframe>element via the
embedattribute. Instead, the
<iframe>should now be placed in between the opening and closing shortcode tags like so:
[map] ... [/map].
[x_audio]– This shortcode has been split into two shortcodes now,
[x_audio_player], which is to be used for self hosted audio, and
[x_audio_embed], which is to be used for embedding third-party audio.
[x_video]– This shortcode has been split into two shortcodes now,
[x_video_player], which is to be used for self hosted video, and
[x_video_embed], which is to be used for embedding third-party video.
No notes available.
No notes available.
No notes available.
No notes available.
No notes available.
No notes available.
No notes available.
No notes available.
No notes available.
No notes available.