Jump to content

  • You cannot start a new topic
  • You cannot reply to this topic

Update Your Add-Ons And Themes To Cs-Cart 4.3.6 Rate Topic   * * * * * 1 votes

 
  • yakulakov
  • CS-Cart
  • CS-Cart Architects
  • Join Date: 26-Jan 15
  • 92 posts

Posted 01 March 2016 - 12:56 PM #1

Hello!

 

Version 4.3.6 is on its way with PHP 7 support and new cool Multi-Vendor features. And meanwhile, check out developer changes for the new version and be ready to adapt your add-ons and themes.

 

Common changes

  • Minimal PHP version requirement bumped from 5.3.0 to 5.3.6
  • PHP7 compatibility implemented
  • PHP7 APCu cache driver added
  • Mysqli DB driver now doesn't suppress "mysqli" class constructor errors
  • You may now install and use symlinked add-ons under the CS-Cart installation directory. This is useful when you develop an add-on in a separate Git repository and create symbolic links of an add-on files under the CS-Cart root directory.
  • Debugger panel now supports EXPLAIN FORMAT=JSON automatically if you use MySQL 5.7
  • Now every block cache parameter can be adjusted via the "app/schemas/block_manager/block_cache_properties.php" schema. Earlier only the "update_handlers" parameter could.
  • Debugger SQL formatting was broken, now it's completely awesome
  • Now Bootstrap::sendHeaders() method doesn't send cache-restricting headers "Expires", "Last-Modified", "Cache-Control", and "Pragma". Sending those headers is delegated to the session_start() function call. It will send correct headers based on the session.cache_limiter PHP configuration parameter value.
  • Service providers pattern was implemented. Provider classes are stored at the \Tygh\Providers namespace and are registered in the init.php file.
  • Database connection class was refactored and was moved to the Application service locator as a component. It's available now as Tygh::$app['db'].

- \Tygh\Database now doesn't contain any logic and proxies all method calls to the Tygh::$app['db'] component

- All database functions such as db_query are still working like earlier, but they now use internally new component

- All of your code will work as earlier, but the \Tygh\Database class is now deprecated and iwill be removed in the next major release (5.x)

- You may now use several DB connections transparently by adding one more DB connection component to the service locator:

// Create a new instance of connection
Tygh::$app['replication_db'] = new \Tygh\Database\Connection(new \Tygh\Backend\Database\Pdo());

// Establish connection to the DB
Tygh::$app['replication_db']->connect('user', 'password', 'localhost', 'db_name', array('table_prefix' => 'cscart_'));

// Run queries!
$user = Tygh::$app['replication_db']->getRow('SELECT * FROM ?:users WHERE user_id = ?i', 1);

- You may want to take a look at the "app/Tygh/Providers/DatabaseProvider.php" and "app/Tygh/Database/Connection.php" files for deeper understanding of internal mechanisms

  • Debugger and On-site editing templates were moved to the backend area
  • The "backend" Smarty template resource was implemented, you can fetch or display backend template with an elegant syntax: php \Tygh::$app['view']->display('backend:views/debugger/debugger.tpl');
  • \Tygh\Http class:

-  The encoding extra parameter was added for cURL requests, it stands for CURLOPT_ENCODING parameter

- Multi-requests no longer trigger 100% CPU usage

  • Working with sessions and session data is now realized through the Tygh::$app['session'] component

- Code for writing into a session: php Tygh::$app['session']['cart'] = array(); Tygh::$app['session']['cart']['products'][] = array(); 

Code for reading from a session: php $cart = Tygh::$app['session']['cart']; // or by link $cart = & Tygh::$app['session']['cart'];  It works the same way as working with $_SESSION directly. However, Tygh::$app['session'] belongs to the \Tygh\Web\Session class. This class replaces the old \Tygh\Session and allows to address to session data with the array syntax. The old Tygh\Session class is deprecated. However, it still works, because it proxies all method calls to the Tygh::$app['session']. We have replaced the usage of '\Tygh\Session with Tygh::$app['session'] in the core and default add-ons. The code that uses $_SESSION` directly may not work as intended with full-page caching turned on.

 

We also implemented service providers. A service provider is a class, an instance of which registers any components and values in the Application container (also known as Service Locator).

 

We added the \Tygh\Providers namespace and the first provider \Tygh\Providers\SessionProvider, that registers the values of session, session.storage and session.storage.class in the container.

  • Code related to archiving and unpacking was refactored and moved to the \Tygh\Tools\Archivers namespace. All existing functions now internally use the new code with backward compatibility preserved. Also, the Archive_Tar class was re-included into CS-Cart and is used as a fallback in case of PharData class fails to perform.

Hook changes

New hooks

  • fn_set_hook('render_block_pre', $block, $block_schema, $params, $block_content); - Allows to perform any actions before actually rendering a block
  • fn_set_hook('render_block_post', $block, $block_schema, $block_content, $load_block_from_cache, $display_this_block, $params); - Allows to perform any actions after actually rendering a block
  • fn_set_hook('registry_save_pre', self::$_changed_tables, self::$_cached_keys); - Hook is executed before saving cache data to persistent storage and clearing expired cache
  • fn_set_hook('settings_update_value_by_id_pre', $this, $object_id, $value, $company_id, $execute_functions, $data, $old_data, $table); - Hook is executed before updating a setting value by setting an object ID
  • fn_set_hook('settings_update_value_by_id_post', $this, $object_id, $value, $company_id, $execute_functions, $data, $old_data, $table); - Hook is executed after updating a setting value by setting an object ID
  • fn_set_hook('buy_together_update_chain_pre', $item_id, $product_id, $item_data, $auth, $lang_code); - Modifies product chain update parameters
  • fn_set_hook('buy_together_update_chain_post', $item_id, $product_id, $item_data, $auth, $lang_code); - Modifies product chain update results
  • fn_set_hook('buy_together_get_chains_pre', $parms, $auth, $lang_code); - Modifies product chains get parameters
  • fn_set_hook('buy_together_get_chains', $params, $auth, $lang_code, $fields, $conditions, $joins); - Change selection condition (fields, conditions, joins) before selecting a payment method data
  • fn_set_hook('buy_together_get_chains_post', $params, $auth, $lang_code, $chains, $fields, $conditions, $joins); - Gets function result along with parameters and query information
  • fn_set_hook('get_discussion_posts_pre', $params, $items_per_page); - Modifies request parameters for fetching discussion posts
  • fn_set_hook('get_discussion_posts', $params, $items_per_page, $fields, $join, $condition, $order_by, $limit); - Modifies discuission posts query
  • fn_set_hook('get_discussion_posts_post', $params, $items_per_page, $posts); - Modifies discussion posts and request parameters
  • fn_set_hook('delete_discussion_pre', $object_id, $object_type); - Modifies discussed object properties
  • fn_set_hook('delete_discussion_post', $object_id, $object_type, $is_deleted); - Modifies deletion results
  • fn_set_hook('discussion_delete_post_pre', $post_id); - Modifies deleting discussion post identifier
  • fn_set_hook('discussion_delete_post_post', $post_id); - Modifies deleted discussion post identifier
  • fn_set_hook('get_discussion_titles', $discussion_object_titles); - Modifies title strings for different discussion types.
  • fn_set_hook('image_zoom_check_image_post', $file_path, $image_data, $images); - Post hook for checking a detailed image sizes ration
  • fn_set_hook('update_addon_status_pre', $addon, $status, $show_notification, $on_install, $allow_unmanaged, $old_status, $scheme); - Hook is executed before changing an add-on status (i.e. before an add-on enabling or disabling).
  • fn_set_hook('update_addon_status_post', $addon, $status, $show_notification, $on_install, $allow_unmanaged, $old_status, $scheme); - Hook is executed after changing an add-on status (i.e. after an add-on enabling or disabling).
  • fn_set_hook('filter_product_data', $request, $product_data); - Filters product data
  • fn_set_hook('top_menu_form_pre', $top_menu, $level, $active); - Modifies top menu forming parameters
  • fn_set_hook('top_menu_form_post', $top_menu, $level, $active); - Modifies top menu items
  • fn_set_hook('update_customization_mode', $modes, $enabled_modes, $available_modes); - Hook is executed before saving enabled customization modes to DB.
  • fn_set_hook('get_predefined_statuses', $type, $statuses, $status); - Prepares statuses for particular object type
  • fn_set_hook('change_company_status_pre', $company_id, $status_to, $reason, $status_from, $skip_query, $notify); - Actions before a company status change
  • fn_set_hook('change_company_status_before_mail', $company_id, $status_to, $reason, $status_from, $skip_query, $notify, $company_data, $user_data, $result); - Actions between changing a company status and sending an e-mail
  • fn_set_hook('create_company_admin_pre', $company_data, $fields, $notify); - Actions before creating a company admin
  • fn_set_hook('create_company_admin', $company_data, $fields, $notify, $user); - Actions before creating a company admin directly 
  • fn_set_hook('create_company_admin_post', $company_data, $fields, $notify, $user); - Actions after creating a company admin
  • fn_set_hook('dispatch_before_send_response', $status, $area, $controller, $mode, $action); - Allows to perform actions before an HTTP response is sent to the client. This is the last place where you can modify the HTTP headers list.
  • fn_set_hook('mve_place_order_post', $order_id, $action, $order_status, $cart, $auth, $order_info, $company_data, $data, $payout_id); - Actions after saving a vendor payout

 

 

 

Changed hooks

 

  • fn_set_hook('top_menu_form', $v, $type, $id, $use_name); is now deprecated
-fn_set_hook('render_block_content_after', $block_schema, $block, $block_content);
+fn_set_hook('render_block_content_after', $block_schema, $block, $block_content, $params, $load_block_from_cache);
-fn_set_hook('get_categories_after_sql', $categories, $params);
+fn_set_hook('get_categories_after_sql', $categories, $params, $join, $condition, $fields, $group_by, $sortings, $sorting, $limit, $lang_code);
-fn_set_hook('get_category_data', $category_id, $field_list, $join, $lang_code);
+fn_set_hook('get_category_data', $category_id, $field_list, $join, $lang_code, $conditions);
-fn_set_hook('clone_product_option_post', $from_product_id, $to_product_id, $from_global_option_id, $v);
+fn_set_hook('clone_product_option_post', $from_product_id, $to_product_id, $from_global_option_id, $option_data, $change_options, $change_variants);
-fn_set_hook('delete_status_pre', $status, $type, $can_delete);
+fn_set_hook('delete_status_pre', $status, $type, $can_delete, $is_default, $status_id);
-fn_set_hook('delete_status_post', $status, $type, $can_delete);
+fn_set_hook('delete_status_post', $status, $type, $can_delete, $is_default, $status_id);
-fn_set_hook('update_image', $image_data, $image_id, $image_type, $images_path, $_data);
+fn_set_hook('update_image', $image_data, $image_id, $image_type, $images_path, $_data, $mime_type);
-fn_set_hook('mve_place_order', $order_info, $company_data, $action, $__order_status, $cart, $_data);
+fn_set_hook('mve_place_order', $order_info, $company_data, $action, $order_status, $cart, $data, $payout_id, $auth);

 

 

 

Core functions

Changed functions

  • \Tygh\Themes\Styles::getCustomFonts() became public
  • \Tygh\Tools\Url::__construct() now can be called without any arguments
  • fn_exim_set_quotes() is now deprecated in favour of fn_exim_quote()
  • fn_companies_change_status() is now deprecated in favour of fn_change_company_status()
-public static function sanitizeData(array $data, array $rules, array $disabled_actions = array())
+public static function sanitizeData(array $data, array $rules, array $disabled_actions = array(), &$changed = false)
-function fn_install_addon($addon, $show_notification = true, $install_demo = false)
+function fn_install_addon($addon, $show_notification = true, $install_demo = false, $allow_unmanaged = false)
-function fn_update_addon_status($addon, $status, $show_notification = true, $on_install = false)
+function fn_update_addon_status($addon, $status, $show_notification = true, $on_install = false, $allow_unmanaged = false)
-function fn_get_subcategories($category_id = '0', $lang_code = CART_LANGUAGE)
// backward compatibility preserved
+function fn_get_subcategories($category_id = '0', $params = array(), $lang_code = CART_LANGUAGE)
-function fn_delete_status($status, $type)
+function fn_delete_status($status, $type, $is_default = false)
-function fn_create_theme_logos_by_layout_id($theme_name, $layout_id = 0, $company_id = null, $for_company = false, $style_id = '')
+function fn_create_theme_logos_by_layout_id($theme_name, $layout_id = 0, $company_id = null, $for_company = false, $style_id = '', $whitelist_of_logo_types = null)
-function fn_get_logos($company_id = null, $layout_id = 0, $style_id = '')
+function fn_get_logos($company_id = null, $layout_id = null, $style_id = null)
-function fn_generate_thumbnail($image_path, $width, $height = 0, $lazy = false)
+function fn_generate_thumbnail($image_path, $width, $height = 0, $lazy = false, $return_rel_path = false)
-function fn_login_user($user_id = '')
+function fn_login_user($user_id = 0, $regenerate_session_id = false)

 

 

 

 

New functions

  • \Tygh\Themes\Styles::createMissedLogoTypesForLayout($layout_id, $style_id)- Creates logos of missing logo types for a given layout and style.
  • \Tygh\Themes\Themes::setManifest($manifest_data) - Sets theme manifest contents.
  • \Tygh\Themes\Themes::getSettingsOverrides($lang_code = CART_LANGUAGE) - Gets theme setting overrides
  • \Tygh\Themes\Themes::overrideSettings($settings = null, $company_id = null) - Overrides settings values from a theme manifest file
  • \Tygh\Themes\Themes::cloneAs($clone_name, $clone_data = array(), $company_id = 0) - Creates a clone of a theme.
  • \Tygh\Registry::getAll() - Returns all variables stored in the registry
  • \Tygh\Registry::getAll() - Returns all cache keys
  • \Tygh\Tools\Url::setHost()
  • \Tygh\Tools\Url::setQueryString()
  • \Tygh\Tools\Url::getQueryString()
  • \Tygh\Tools\Url::setPath()
  • \Tygh\Tools\Url::getPath()
  • \Tygh\Tools\Url::containsAsSubpath(self $url) - Checks if a given URL is a subpart of the current URL by matching their paths
  • fn_image_zoom_check_image(&$image_data, &$images) - Checks a detailed image sizes ration
  • fn_seo_get_canonical_links($base_url, $search) - Generates SEO Canonical, Prev, Next links
  • fn_exim_quote(&$value, $quote = "'")
  • fn_exim_apply_company($pattern, &$alt_keys, &$object, &$skip_get_primary_object_id) - Adds the current company_id as altkey if an object doesn't have store defined. Needed to determine the primary object correctly.
  • fn_promotions_filter_data($data) - Filtration conditions and bonus values
  • fn_promotions_filter_conditions($conditions) - Filtration conditions values
  • fn_promotions_filter_bonuses($bonuses) - Filtration bonus values
  • fn_get_addon_layouts_path($addon_name, $theme_name = '[theme]') - Returns path to the add-on layouts file in a specified theme
  • fn_store_shipping_rates($order_id = 0, &$cart, $customer_auth) - Stores shipping rates when managing an order
  • fn_filter_product_data(&$request, &$product_data) - Filters product data before saving
  • fn_check_change_store_mode_permission() - Checks permission for the store mode change
  • fn_get_predefined_statuses($type, $status = '') - Gets a list of the predefined statuses for a particular object type
  • fn_delete_status_by_id($status_id) - Deletes a status, its description, and data by the status identifier
  • fn_get_status_id($status, $type, $is_default = null) - Returns a status identifier by the status code and type
  • fn_get_statuses_by_type($type) - Returns statuses of a specified type
  • fn_change_company_status($company_id, $status_to, $reason = '', &$status_from = '', $skip_query = false, $notify = true) - Changes a company status. Allowed statuses are A(ctive) and D(isabled).
  • fn_create_company_admin($company_data, $fields = '', $notify = false) - Creates a company admin
  • fn_check_current_user_access($permission) - Checks if the current user has access to the specified permission


 
  • zynch
  • Newbie
  • Trial users
  • Join Date: 29-Feb 16
  • 1 posts

Posted 04 March 2016 - 05:12 AM #2

Would there be any template / styling changes to be aware of?



 
  • imac
  • CTO
  • CS-Cart Architects
  • Join Date: 22-Nov 05
  • 2033 posts

Posted 04 March 2016 - 12:17 PM #3

Would there be any template / styling changes to be aware of?

No, at least for 4.3.6.

What would you like to see in such changes? are you a theme developer?


Ilya Makarov,
CS-Cart Architect Team
Suggest and vote for new features | Report a bug

 

Posted 04 March 2016 - 04:31 PM #4

Ilya, in a recent post, you suggested that there were changes coming to the shipping function for Multi Vendor. I agree with the post that pointed out that the current way shipping works in not practical for a Multi Vendor application. 

 

Is there a development plan to allow Vendors to specify their own shipping methods and fixed rate shipping charges (as eBay and others)? Similar to Sales Tax, it does not make any sense for the Marketplace Owner to specify such things on behalf of our Vendors.

 

I appreciate that when configured correctly, the shipping calculators can be a very valuable tool, but many Vendors will not make the effort to learn CS Cart's rather complicated shipping set up and would rather just estimate the shipping for each item.

 

Thanks,

 

Stockflo Jeff



 
  • tbirnseth
  • CS Cart Expert
  • Authorized Reseller
  • Join Date: 08-Nov 08
  • 10661 posts

Posted 04 March 2016 - 08:38 PM #5

*
POPULAR

- All of your code will work as earlier, but the \Tygh\Database class is now deprecated and will be removed in the next major release (5.x)

 

Are you really going to deprecate all the DB functions (db_query, db_get_fields, db_get_hash_array, etc.) and force addon developers to again have to completely rewrite their addons?  You should be preserving compatibility, not eliminating it.

 

Seems like the vast majority of changes in the Common area relate to supporting common code for Merchium rather than adding any real value to cs-cart.

 

Looks like Version 4X will be the last of the addons I produce for cs-cart.


EZ Merchant Solutions: Custom (USA based) B2B Development, Consulting, Development and Special Projects (get a quote here).
Commercial addons, payment methods and modifications to meet your business and operations needs.


 
  • Flow
  • Super Duper and Amazingly Sexy Senior
  • Members
  • Join Date: 13-Oct 10
  • 2099 posts

Posted 04 March 2016 - 09:31 PM #6

Are you really going to deprecate all the DB functions (db_query, db_get_fields, db_get_hash_array, etc.) and force addon developers to again have to completely rewrite their addons?  You should be preserving compatibility, not eliminating it.

 

 

This!! What Tony says. CS-cart, you are destroying your own business if you keep rendering our custom work unusable. You don't want to know how much time and money we spent on making add-ons and a design for v3 - I didn't even make it in time because then version 4 came out - and we had to start all over again. It's so, so, so stupid pissing off your users and customers like this. I just do not get it. Stick to version 4 - make it rock solid. That is what we want. We don't need yet another buggy new kid on the block that we can only start using at version 5.35.


When life hands you lemons, bring on the Tequila baby!


 
  • tbirnseth
  • CS Cart Expert
  • Authorized Reseller
  • Join Date: 08-Nov 08
  • 10661 posts

Posted 04 March 2016 - 11:49 PM #7

It could be that they are referring ONLY to the Database *class* and not the functions that live on top of them.  I certainly hope so.

Trouble is small operations like myself simply don't generate enough sales to warrant rewrites of everything every 2 years.   As I said, many of the changes seem to be more to support (or stay consistent with) Merchium and I'm struggling to see the value added to cs-cart of these changes versus the risk they inject.

 

The 45 day defect correction also seems to have gone by the wayside again....  Developers just stop responding when they don't want to hear it any more (like their fix didn't work or didn't address the problem or they didn't understand the problem).


EZ Merchant Solutions: Custom (USA based) B2B Development, Consulting, Development and Special Projects (get a quote here).
Commercial addons, payment methods and modifications to meet your business and operations needs.


 
  • Darius
  • Douchebag
  • Members
  • Join Date: 20-Apr 08
  • 3155 posts

Posted 05 March 2016 - 08:42 AM #8

Wow did not expect this coming. So much expectations for Merchium but by looking at their forum it does not look live..

 

 

 

Seems like the vast majority of changes in the Common area relate to supporting common code for Merchium rather than adding any real value to cs-cart.

 

Looks like Version 4X will be the last of the addons I produce for cs-cart.



 
  • steve22
  • Junior Member
  • Authorized Reseller
  • Join Date: 10-Aug 09
  • 178 posts

Posted 09 March 2016 - 04:56 AM #9

we also would need to evaluate CS cart as a whole, the market is already so small, forcing us to re-write all of our quite comprehensive addons will likely mean that we will rather concentrate on Magento


[size=5]4Sprung web development[/size]
67 Botany Rd Waterloo NSW Sydney Australia
for over 19 years we provide everything e-commerce. Over 20.000h CS Cart Development Expirience

 
  • ThomH
  • Senior Member
  • Members
  • Join Date: 20-Nov 07
  • 1448 posts

Posted 09 March 2016 - 09:01 AM #10

No so good news...


WebGraphiq offers a wide range of professionally developed, ready to use CS-Cart add-ons to provide additional functionality and boost your sales. The oldest active CS-Cart add-on development team. -- Since 2006 --


CS-CART ADD-ONS | FREE QUOTE | CS-CART DEVELOPMENT | @webgraphiq


 
  • imac
  • CTO
  • CS-Cart Architects
  • Join Date: 22-Nov 05
  • 2033 posts

Posted 30 March 2016 - 01:01 PM #11

Are you really going to deprecate all the DB functions (db_query, db_get_fields, db_get_hash_array, etc.) and force addon developers to again have to completely rewrite their addons?  You should be preserving compatibility, not eliminating it.

 

Seems like the vast majority of changes in the Common area relate to supporting common code for Merchium rather than adding any real value to cs-cart.

 

Looks like Version 4X will be the last of the addons I produce for cs-cart.

 

 

This!! What Tony says. CS-cart, you are destroying your own business if you keep rendering our custom work unusable. You don't want to know how much time and money we spent on making add-ons and a design for v3 - I didn't even make it in time because then version 4 came out - and we had to start all over again. It's so, so, so stupid pissing off your users and customers like this. I just do not get it. Stick to version 4 - make it rock solid. That is what we want. We don't need yet another buggy new kid on the block that we can only start using at version 5.35.

 

 

we also would need to evaluate CS cart as a whole, the market is already so small, forcing us to re-write all of our quite comprehensive addons will likely mean that we will rather concentrate on Magento

 

 

No so good news...

Guys,

 

all "db_" functions will work as before in 4.4, 5.x or any future version.

No plans to change them.

 

What we changed is class Database, in order to be able to mock it for unit testing.

 

So if earlier in any "db_" there was: 

return call_user_func_array(array('\\Tygh\\Database', 'query'), func_get_args());

than now its:

return call_user_func_array(array(Tygh::$app['db'], 'query'), func_get_args());

That's all.

 

I apologise we confused you.


Ilya Makarov,
CS-Cart Architect Team
Suggest and vote for new features | Report a bug

 
  • pradeesh_72
  • Member
  • Trial users
  • Join Date: 15-Nov 17
  • 42 posts

Posted 04 January 2018 - 12:25 PM #12

Can I use dispatch_before_send_response hook to overwrite the homepage content for specific set of users?



 
  • eComLabs
  • CS-Cart Expert
  • Authorized Reseller
  • Join Date: 27-Jan 14
  • 17581 posts

Posted 04 January 2018 - 01:44 PM #13

Can I use dispatch_before_send_response hook to overwrite the homepage content for specific set of users?

 

What part of the page do you want to override?


GET A FREE QUOTE | CS-Cart Add-ons | CS-Cart Licenses | CS-Cart Development | CS-Cart Design | Server Configuration | UniTheme and YOUPI
CS-Cart                USD 345     Multi-Vendor              USD 1250    CS-Cart RU                         24500 руб.
CS-Cart Ultimate  USD 775     CS-Cart + YOUPI      USD 545      CS-Cart RU + UniTheme    36000 руб.


 
  • tbirnseth
  • CS Cart Expert
  • Authorized Reseller
  • Join Date: 08-Nov 08
  • 10661 posts

Posted 04 January 2018 - 07:45 PM #14

Why woudn't you use the "index:content" hook instead?  I.e.

[code=auto:0]

{if $my_logic_for_override}

<!-- my content goes here -->

{/if}

{/code]

And you'd use design/themes/[YOUR THEME]/templates/addons/[YOUR ADDON]/hooks/index/body.content.tpl

 

Note that if an 'override' returns no content then it is ignored.


EZ Merchant Solutions: Custom (USA based) B2B Development, Consulting, Development and Special Projects (get a quote here).
Commercial addons, payment methods and modifications to meet your business and operations needs.


 
  • pradeesh_72
  • Member
  • Trial users
  • Join Date: 15-Nov 17
  • 42 posts

Posted 05 January 2018 - 04:48 AM #15

Am skeptical about using tpl hook. Mainly because what I want is something similar to twigmo functionality. The layout should be configurable. I will have a set of user groups, and for each group the homepage will be different. Deafult homepage will have one layout and the other set of users will see a completely different layout. Moreover, there is no actual "Content" in homepage for cs-cart. It's all blocks displayed at different places. So in that case, a if else condition in the body.content.tpl will not serve my purpose, though that could be a last resort.



 
  • eComLabs
  • CS-Cart Expert
  • Authorized Reseller
  • Join Date: 27-Jan 14
  • 17581 posts

Posted 05 January 2018 - 07:26 AM #16

Please pay attention to our Additional Block Settings module. With this addon you can display blocks for necessary user groups

 

These blocks are not just hidden by CSS but not retrieved from database


GET A FREE QUOTE | CS-Cart Add-ons | CS-Cart Licenses | CS-Cart Development | CS-Cart Design | Server Configuration | UniTheme and YOUPI
CS-Cart                USD 345     Multi-Vendor              USD 1250    CS-Cart RU                         24500 руб.
CS-Cart Ultimate  USD 775     CS-Cart + YOUPI      USD 545      CS-Cart RU + UniTheme    36000 руб.


 
  • tbirnseth
  • CS Cart Expert
  • Authorized Reseller
  • Join Date: 08-Nov 08
  • 10661 posts

Posted 05 January 2018 - 09:04 PM #17

Or alternatively in your override hook:

{assign var="alt_groups" value=[7, 9, 13] }
{if $alt_groups|array_intersect:$auth.usergroup_ids}
<!-- Display template(s) for your alternate groups -->
{/if}

 

If the user is in usergroup_id 7, 9 or 13 then the array_intersect will be true.

If not, then the block(s) will be ignored because it has no content and the standard blocks from the homepage location would be used.


EZ Merchant Solutions: Custom (USA based) B2B Development, Consulting, Development and Special Projects (get a quote here).
Commercial addons, payment methods and modifications to meet your business and operations needs.