To install this theme you must have a working version of WordPress already installed. For information in regard to installing the WordPress platform, please see the WordPress Codex article on installation.
To update using the Envato market plugin:
Go to Envato market plugin and click 'generate a personal token' to add your token if you haven't already. You will be transferred to Envato Market's site in order to generate your token.
On that page, you can leave the permissions at their defaults. Grab your token and paste it in the 'Token' text box and click 'Save Changes'.
After that you should see all your purchases from Envato in the plugin's page, and have the option to update in one click:
]]>UXSHOP comes with the ability to bulk install all required and recommended plugins.
Once you have activated the theme you will be prompted to install and activate the required and recommended plugins.
Simply click Install "Begin installing plugins" and the process will begin. You can start the same process by navigating to Appearance->Install Plugins.
]]>This theme has the ability to import a demo content package in 1 click.
Before importing demo content make sure you have installed and activated all the required plugins, and any of the recommended you are planning to use.
It is also recommended to finish the WooCommerce setup wizard before importing. You should import on a new, clean install of Wordpress.
To import demo content head over to the Demo Importer section in the theme's options panel. There you can just click 'import demo' in any of the demos you see listed. Wait for the process to finish and don't refresh the page until it does.
When the page refreshes navigate to your home page and the check that the demo has been imported correctly.
Note that the stock imagery used in the theme’s demos are not coming with the importable content that will replicate the layouts you see there. They’re replaced with blanks so you can easily replace the images with yours. You are now ready to start replacing the demo content with your own.
]]>Child themes are the recommended way of modifying an existing theme.
You can download a starter child theme for UX Shop here.
This child theme can be installed along side the UX Shop theme and will point to it as the parent. It includes a commented style.css and a functions.php with no other customization.
]]>This process give you the ability to have a shop in a single language. In order to have a multilingual shop, you need to use WPML (premium plugin, sold separately).
After installing Loco translate you can find the theme's text strings under Loco translate > Themes.
Check out this video for an example on how to translate the 'No products in cart' string in the drop-down shopping cart:
Hint: If you are having trouble translating the drop-down Cart's contents, try changing the items included in the cart, by adding/removing a product, in order to clear the internal WooCommerce cart cache.
]]>This functionality is build in into a separate plugin ( named: Typekit for Redux Framework, by develoved ) which is bundled with the theme and can be installed easily through the required & recommended plugins installer ( Appearance -> Install plugins ).
See Installing required & recommended plugins for more.
To create a Kit, check out this link. Once you have created a kit, you have to get the Kit's ID. Launch the Kit editor and click the 'Embed' link near the top right corner: On the modal box that pops up you can see your Kit's ID. Copy it down.
If you don't hit the Refresh & show kit fonts button the changes to the font list won't take effect.
If everything works, the fonts configured in your kit should appear right below the button: If you don't see your fonts, make sure that:
If you are having issues with FOUT (Flash of unstyled text, the text is shown briefly before the font has been downloaded), you can enable this option and reveal the page only after the font has been downloaded.
After you have set-up the kit in the theme's options and saved your changes, do a page refresh and go to the Styling->Fonts settings section. Open any of the Font selector dropdowns and you should see the Typekit fonts from your Kit!
]]>
The dimensions of the sections slider are determined by the container it is in, and by the contents of it. If you want to set the width of the Section slider to be equal to the full window width, since it is contained in a Visual Composer row, you must go into that's row settings and set it to 'Stretch row and content (no paddings)'
On the other hand if you want to set the height of the section slider, lets say to 100% the window height, you must set the height of each one of the slides. The Sections Slider will automatically adust it's height to match the visible slide's height.
So to set the Section Slider to match the window's height, you must set each slide to match the window's height. You must do that by setting the Full height row to 'Yes' in the Row settings of the row that contains the section's content. In this case you should have only one (outer) row.
Also on the meta box 'General Section Settings' you should set Height / Padding to No padding, and check Full Width
]]>B. Full width mega menu, where the menu's container is 100% of the window size, it's background color is the header's background color (solid color), and the menu columns total width, is the grid's width.
For example, if you have 2 menu columns, each of them will 50% the grid's width.
When the screen's width is smaller than this setting, it has no effect. Eg. on a tablet with a 768px wide display, the grid will be at a maximum of 768px.
Setting an explicit value in Pixels is recommended, although this field can also accept % values. Setting for example 'Max Grid width' to 100% will make the grid always as wide the browser's window.
The offset refers to the initial position of the background image. You can use positive or negative values to achieve the desired effect. The cover height can be set in one of three modes: Contents+padding, Window Height and Custom. When 'Contents+padding' mode is selected you can explicitly set the top & bottom paddings.
For example, a value of 'Overlay opacity (min)' = 50 and 'Overlay opacity (max)' = 100 will make the coverlay 50% visible initially and 100% visible when it almost out of view.
You can also achieve the opposite effect, making the overlay dissappear as you scroll away from the page cover, by setting the min value larger than the max.
invisible
class.
To do that, you have to reveal the classes property when you are editing the respective menu:
And in the column you want to hide add the invisible
class:
]]>
]]>
<script> ..... </script>
)
And paste the copied code into Custom Map style option back in the theme's settings.
The order is important and the first line should always have the largest number and the 'At least' setting.
This affects the product list, ( product categories view - product archives ), and all other locations, eg Related Products in single view, Products sliders (shortcodes), where the value is not overriden by the individual location settings.
In cases where there is only one setting, e.g. for the number of columns in a products slider, that settings overrides only the initial (the At least...) setting for the grid layout.
So if for example you create a product slider and set the columns in the Element's settings to '6' and you have in your theme settings the values shown above, when the screen width is larger than 1201px, the columns will be 6, when the screen width is smaller than 1200px the columns will be 3, smaller than 992px the columns will be 2, and so on.
You should choose these values with consideration on how your product images show in various screen widths, in relation to your settings about sidebar visibility, and site's grid width. Leave the defaults if you are not sure.
]]>
Eg. with the settings shown above, the slider will cycle through 7 products, but only the 5 will be visible (5 columns in the slider).
]]>This functionality is build in into a separate plugin ( named: Pagesections by Develoved ) which is bundled with the theme and can be installed easily through the required & recommended plugins installer ( Appearance -> Install plugins ).
See Installing required & recommended plugins for more.
Examples of where you can use page Sections are in all pages or certain templates by setting the appropriate option throught theme options (see for example, Header->Header Sections in the theme's options panel), right before the footer, inside the footer and/or the socket and in ANY place you can add content using the Visual Composer. Using the Visual Composer you can add a Page Section using the 'Section' element.
You can also add multiple page sections in the 'Sections Slider' element and easily create a simple slider.
]]>
function uxs_child_remove_product_tabs( $tabs ) { unset( $tabs['additional_information'] ); // Remove the additional information tab return $tabs; } add_filter( 'woocommerce_product_tabs', 'uxs_child_remove_product_tabs', 98 );]]>
Google Maps changed their policy and began enforcing the use of API keys, effective June 11, 2018
A Google API key is required to render Google Maps. You can check this link on how to create one or the official guide.
Once you have your API key you need to enter it to the Google API key field under UX Shop > Advanced for the maps to render correctly.
(Remember to download the zip file containing only the theme , and not the complete package).
This will have the same results as automatically updating the theme.
-or-
Author: develoved
to
Author: ioDSGN
Afterwards the Envato Market plugin should give you the option to update.
If you are having trouble with this procedure, please open a support ticket.