About cookies

Items 1 to 20 of 178 total

per page

Set Ascending Direction
  • Magento Community (社区版本) 1.5.0.0, Professional (专业版本) 1.10.0.0, Enterprise (企业版本) 1.10.0.0 发布

    6 year(s) ago

    最新版本的 Magento 平台已经发布,此次发布包括社区版本 Magento Community Edition 1.5.0.0, 专业版本 Magento Professional 1.10.0.0, 企业版本 Magento Enterprise 1.10.0.0

    以下是这次新版本发布释出的重要功能和特性:

    • 大幅改进的产品和用户导入导出功能
    • 后台创建或修改订单时能够添加和管理组合产品
    • 增强了购物车使之支持编辑产品配置
    • 增强了 wishlist 功能
    • 可选择文件系统或数据库存储媒体
    • 集成 PayFlowLink HSS
    • 升级 Zend Framework 到 1.11.1
    • 增强了 core API 包括 exposing shopping cart API
    • 以及更多...

    这次发布包括新版本的 Magento Connect Manager (MCM), 这个页面 介绍了新的特性以及如何升级到新版本的 Magento Connect Manager.

    要查看全部的特性列表和已修复的问题请到我们的 发布说明页, Diff 文件可以在 这里 找到.

    转到 下载页面 下载最新版本的 Magento 或通过 SVN 更新.

    除此之外,企业版本 1.10.0.0 添加了重大的改进到我们的礼品功能, 包括出色的产品级别和订单级别的礼物包装选项, 多种包装价格, 以及礼品包装图片.

    专业版本和企业版本的客户及客户请访问支持站获取更多此次发布的信息.

  • PHP bug #53632 验证方法

    6 year(s) ago

    以下命令在命令行运行用于测试bug是否存在。
    这个bug会导致服务器FPU停止。(X87 CPU)
    
    <?php
    /*
      +----------------------------------------------------------------------+
      | PHP Version 5                                                        |
      +----------------------------------------------------------------------+
      | Copyright (c) 2011 The PHP Group                                     |
      +----------------------------------------------------------------------+
      | This source file is subject to version 3.01 of the PHP license,      |
      | that is bundled with this package in the file LICENSE, and is        |
      | available through the world-wide-web at the following url:           |
      | http://www.php.net/license/3_01.txt                                  |
      | If you did not receive a copy of the PHP license and are unable to   |
      | obtain it through the world-wide-web, please send a note to          |
      | license@php.net so we can mail you a copy immediately.               |
      +----------------------------------------------------------------------+
      | Author: Johannes Schlueter <johannes@php.net>                        |
      +----------------------------------------------------------------------+
    */
    
    if (PHP_SAPI != 'cli') {
        die("Please run this test from CLI!\n");
    }
    
    ini_set('display_errors', 1);
    ini_set('output_buffering', 0);
    error_reporting(-1);
    if (!ini_get('safe_mode')) {
        set_time_limit(1);
    }
    
    echo "Testing float behaviour. If this script hangs or terminates with an error ".
         "message due to maximum execution time limit being reached, you should ".
         "update your PHP installation asap!\n";
    echo "For more information refer to <http://bugs.php.net/53632>.\n";
    $d = (double)"2.2250738585072011e-308";
    echo "Your system seems to be safe.\n";
    ?>
    

  • 叶朋谈“简单管理”

    6 year(s) ago

    20091104100443547
    
    原发自 FT中文网
    
    叶朋是高原资本的投资董事,此前是百度COO,再之前是苹果中国区总经理。他眼中的互联网和管理又是如何?
    
    程:您的管理经验有总结吗?
    
    叶:三个词:聚焦,简单,100%的执行。
    
    程:听起来很耳熟,不少人都这样总结。请解释下。
    
    叶:聚焦。能做到的前提是抓住行业或问题的本质与重点,否则无法够聚焦。但你怎么能够知道本质和重点?那就需要真正懂得与深刻理解这个行业,明确公司的定位。说定位,无非就是舍得,你要回答清楚:想要什么,放弃什么;是什么,不是什么。一个公司什么都要,就没有定位,就什么都不是。
    
    不少企业家和经理人很忙,就因为工作没有重点。优秀的企业家和经理人是不忙的,他知道哪些工作是不必做的。有些人一旦不忙,就会心慌,忙似乎意味着充实,忙成了这些人追求满足感、安全感的途径。但是他们错了,重要的是在正确的时间,正确的地点做重要和正确的事情,不重要的事情,或者时机不正确是,不需要去做。
    
    程:那简单呢?
    
    叶:所谓完美,就是把不需要的东西全部拿掉,也就是简约至极,大道至简就是这个道理,对人,对事,对公司都是一个道理。要做到简单,必须把上面第一条做到:也就是聚焦。抓住问题的核心是简单的前提,是最有效的方法。抓不住问题的核心就无法做到简单。中学时候学几何,优秀的学生,两三步就解出来了答案,差学生得要十几步。虽然问题都得到解决,但在工作和生活中,十几步是浪费资源,两三步就简单,因为优秀学生抓住了问题的核心。
    
    想要做到简单,有个捷径:招最优秀的人。这是最有效、最省钱的方法。早些年,乔布斯说一个优秀的人能顶10个一般人,后来变了,认为一个优秀的员工能顶50个一般的员工。
    
    程:这跟中国人讲的“三个臭皮匠顶个诸葛亮”的谚语不一致。
    
    叶:乔布斯的说法有其道理。第一是工资成本,一个优秀的人,工资一般就是一般人的2~2倍。第二是沟通成本,要一个优秀的人明白一个事情很容易,但要10个一般人都明白一个事情,难啊。相比而言要花几十倍的时间。而且这10个人之间还要相互沟通,相互说服,对同一事情的理解自然会有不同,因此很难达成真正意义上的一致。第三是产出,最优秀的人才通常能给出最佳的解决方案,这是最重要的一点。最佳的解决方案用最少的时间、最少的资源、达到最大的效果。这里又会节省大量的成本,并有最好的效果。
    
    程:道理是这样,做起来难在哪里。
    
    叶:需要环境。企业是否准备好了去招最优秀的人?比如,老板和团队有没有准备好,有没有足够的胸怀接纳富有个性的优秀人才?如何确保空降人才与现有团队的融合?空降的人才自身是否做好充分的准备融入新的公司?等等。否则即使优秀的人来了,也很难生存。天时地利人和缺一不可,也就是在恰当时间引进恰当人才。引进人才的背景与能力对于企业现阶段的发展如果过于超前,对双方都不合适。
    
    程:最后是执行,确保真正的100%的执行。
    
    叶:一件事情如果没做成,一定要找原因。不能简单的说:决策是错的或者团队不行。一个决策的执行最后失败不外乎有几个原因:一,决策本身是错的,也就是天时地利不对,一开始就注定要失败。这就不是执行的错误。二,应该给予的资源没有给,或者没有给够。三,没有找合适的人去执行这个决策。四,组织架构的每一级、每一个团队是否100%的执行。如果公司有5个层级,每一个层级的执行效果都是90%,5个90%相乘的结果是59%,不及格。要知道,每个层级的90%的执行效果,自以为很不错了,但一迭加,不及格。所以一定要100%执行。以上几点都和人有关,特别是企业的领导者以及管理团队。
    
    作者:程苓峰 http://t.qq.com/chengl
    

  • ]Project-Open[ Partner

    6 year(s) ago

    We are proud to be a partner of ]Project-Open[.

     

    Cosmo Commerce is a open-source IT consulting company based in Shanghai, China.

     

    Cosmo Commerce is the localization lead for the Chinese (simplified) localization of ]project-open[.

     

    What is ]Project-Open[ ?

    ]project-open[ is a global project with users and partners in more than 25 countries. Working with our partners, we are meeting a broad range of project management priorities.

     

    More details please visit:

    http://www.project-open.com

    http://www.project-open.org

  • Magento Best Practice

    6 year(s) ago

    With Our Best Practice you can gain the great converstion rate.

    After several years Magento Service, we now provide following service:

    1 Magento High-End Solutions(Including Deployment,Operation and Integration to exist system. e.g. ERP/CRM/Call Center System)

    2 External System Integration(Payment Gateway/Shipping/ERP/Warehouse/Call Center/CRM integration)

    3 SEM Online Marketing Service(log analyze/process optimization)

    4 Consulting Service(Online Business/System Optimization/Operation Benchmark support/Business Process Management)

    5 Business Intelligence(Data Warehouse/Date Mining)

  • 99Bill Payment Gateway for magento

    6 year(s) ago

    We offered 99Bill Payment Gateway for magento. You can get it at magento-connect or git.

    Magento Connect

    git

    如果您觉得本模块,帮助了您,请支持我们!

    Click here to lend your support to: magento-payment-gateways and make a donation at www.pledgie.com !

    If you like this module,please support us to continue open source!

    99BIll(快钱) : www.99bill.com
    CosmoCommerce: www.cosmocommerce.com

    OpenSource Support Information:
    Email:opensource@cosmocommerce.com
    Tel: +86-021-66346672

    Cosmo Mao

    Welcome your feedback, thanks!

  • Joomla 1.6 发布

    6 year(s) ago

    新的改进集中在:
    
    权限控制,SEO,速度优化,后台操作人性化。
    
    熟悉joomla定制开发的一定会发现其系统的关注点往往围绕着网站管理者,大量的定制在现有框架内是很难进行操作的。
    
    我们很难做出超出系统框架以外的定制开发,例如以前的权限细粒度就不够,一直通过第三方插件完善,但是插件很难做到交互通讯,导致互相间的不兼容(相同的情形在Drupal身上很难发现)
    
    即使有着这些问题,joomla在易用性上依旧高于drupal,我们可以很便捷的将其用于快速开发与原型系统的探讨。
    
    通常情况下,开发joomla需要的时间是1-2周而drupal往往要多出1-2周,甚至更多时间。
    
    这一方面是因为drupal的系统结构更为严谨规范,需要处理更多可扩,可控的部分,另一方面也是因为作为一个网站信息管理系统(CMS)两者的关注点是不同的。
    
    Drupal是从信息交互的角度来看待网站,而Joomla更多的是从信息发布的角度来看待。
    
    所以Drupal的node最强大的地方在交互性操作,而joomla的最强大的地方在于快速的功能模块组件的创建速度上。
    
    学习曲线来看,Drupal也要比Joomla陡。
    

  • Magento 1.5 商品导入导出

    6 year(s) ago

    Magento 1.5 针对商品导入导出的弊端进行了改善。目前商品在属性,自定义选项和导入导出性能上都有了较大改善。

  • Drupal 7 发布

    6 year(s) ago

    代表开源CMS动态灵活的Drupal系列已经发布到7. 目前该系统可以更有效的提供扩展性和后台的人性化操作管理。
    
    在功能上,最显著的变化是:
    
    1 后端db的多样性,可以支持NoSql
    
    2 API的功能增强,外部系统进一步整合
    
    3 自动化代码测试框架
    
    4 支持集群分布式部署,负载压力增强
    
    5 扩展性更好,对views进行支持方便界面调整和定制
    

  • TYPO3 4.2 RC 1 Now Releaesd!

    6 year(s) ago

    The core team is proud to announce the first Release Candidate of TYPO3 version 4.2. After the previous three Beta versions this Release Candidate starts the ramp down of TYPO3 4.2 development.

    So what has changed?

    Bugfixes

    Most of the work since Beta 3 has been spent with fixing bugs. About 100 bugs were fixed. All other fixes are rather minor and can be looked up in the ChangeLog.

    Rich Text Editor

    About a quarter of the fixed issues concerned the Rich Text Editor which should now be more stable and more compatible in general.

    Inline Relational Record Editing (IRRE)

    Another mayor field of work was IRRE with six bugs fixed.

    Developer relevant changes

    Until now it was not possible to xclass certain classes in TYPO3 due to the use of private PHP 5 visibility declaration. All private declaration were replaced with protected declarations and additional XCLASS declarations were added where they were missing.

    Reminder: Raised minimum PHP version requirement

    To run TYPO3 4.2 you need to have at least PHP 5.2. This move was necessary to use PHP features introduced since PHP 5.0.

    As always

    Other then the highlighted bug fixes, performance improvements, and enthusiasm we again put lots of love into this release. A special thanks for the help in making this release what it is goes to the core team and all engaged community developers.

    Next steps to 4.2 final

    As this is a release candidate we strongly recommend this version on your sites. This is now not only recommended to developers but also to all users.

    Please test this release candidate version as much as possible, especially the new features introduced with the previous alpha and beta releases! If you're using one of the new features in a project of yours already and discover bugs, please report them immediately to bugs.typo3.org!

    The next release will be release candidate 2. We will continue releasing RC versions in one week cycles until we feel the code base is good enough for a final release.

    For a detailed overview of the features in 4.2 have a look at the Development wiki page, the bugtracker, and the ChangeLog.

    You can download the packages at typo3.org/download/packages/.

    MD5 Sums:

    ba71231a214a745687504d432004d702  dummy-4.2.0RC1.tar.gz
    9c02f0bedf9f3b2f824c783ca0eab8d3  dummy-4.2.0RC1.zip
    cbc34a0ba33c38e11c15bfb47e3fb11f  typo3_src-4.2.0RC1.tar.gz
    986517d7f1df7330c59ad05f977b34eb  typo3_src-4.2.0RC1.zip
    587f998203e9d3ca0f27b19af3112fb4  typo3_src+dummy-4.2.0RC1.zip

    cheers
    Ingo

  • Magento 1.4.2 发布,更新了Zend框架到1.10.8

    7 year(s) ago

    新的版本发布在 http://www.magentocommerce.com/download/
    
    简要来说这次对插件的查找和更新更加便利。
    
    Zend框架升级后性能会提高一些。
    
    详细的英文介绍查看全文。我们将会稍晚时间进行针对关键功能提出介绍和整合思想。
    
    系统早日看到整合Zend 1.11框架的Magento,这样部署到云环境里可以极大改善运营成本的估计,方便动态调整性能。
    
    
    

    Improvements

    • Added “Switch/Maestro” card type support to centinel 3DS validator. Added comment about maestro and 3d-secure to paypal system config
    • Added more flexible filters implementation in collections * Varien_Data_Collection::addFilter() registers filters as objects and implements getFilter() method to be able to detect/modify already existing filters * Varien_Data_Collection_Db::_renderFilters(): * Added a hook _renderFiltersBefore() * Implemented ‘public’ filter type, which maps the provided filter field from public into internal view and passes the “value” as a condition through _getConditionSql() * Added $this->_renderFilters() call to abstract EAV collection to accommodate the filters that may be set by addFilter() method
    • Added ability to pass multiple recipient emails and names to Mage_Core_Model_Email_Template::send()
    • Backordered Item Status for subitems in Orders * Added correct message at order for all backordered items. At back-end all items shows as backordered if their quantity is below or equal to zero * Fix of duplication backorder messages for composite product options with same backordered item - saving backorder messages per product id
    • Magento Connect Manager * checking cyclic dependency references and conflicts with local files * implemented adding to MCM manually installed extension * changed upgrade logic, previous version of package should be deleted before install new * Implemented new download process and dependencies rules * Added correct behavior during extension reinstall, so dependencies will not reinstall automatically
    • Optimized rewrite selection from DB, added url rewrite and suffix validation at admin backend
    • Added verification of access level for app/etc/local.xml. * Now if server configuration has issue and this file accessible from browser admin user gets notification in backend.
    • Upgraded Zend Framework to version 1.10.8
    • Added the Recurring Profiles tab in customer management
    • Implemented cache for shipping rates and fixing issues with rounding
    • Design packages and themes optimization/refactoring/improvements: * minor improvements and fixes * improved upgrade-ability of CE themes
    • iPhone Theme Refactoring
    • Added Widget settings sharing between widget types
    • For Invoices, Shipment, Credit Memos added possibility to show admin comments at user frontend (checkboxes “Visible on Frontend” in admin interface) * Added JS to enables/disable checkbox ‘Append Comments’ depending on checkbox ‘Email Order Confirmation’ * Refactored invoice/shipment/refund comments collections models to one abstract Comment Collection Model * Refactored Block Order Invoice/Shipment/Creditmemo comments to usage of common block and design - Block Order Comments
    • A little more accurate profiler - important for very quick measurements
    • Add Shopping Cart API
    • Implementing payment refund notifications
    • Added website price scope for bundle items
    • Added support of pending transaction to payflow pro. Also fixed “denied payment review” message in payment
    • Upgraded TinyMCE to v.3.3.7
    • Added to prototype validation by length min-length validation
    • Added Varien.DateElement for front-end date form fields and re-implemented Varien.DOB
    • Added functionality to disable dashboard charts in backend (System > Configuration > Admin > Dashboard)
    • Added functionality to disable dashboard charts during installation
    • Adminhtml W3C Validation improvements
    • Added ability to use session save method from configuration
    • Rendering customer attributes
    • Added favicon manager under System > Configuration > Design > HTML Head

    Changes

    • Refactored shipping rates calculation to keep process solid and do not try to recreate internal process of calculation, as it was
    • Added caching of requests to shipping carriers, because otherwise we get too much duplicate requests during calculation of every shipping method
    • Refactored “Special products” RSS feeed
    • Shortened the names of all foreign keys longer than 49 characters
    • Compilation scope for some EAV models which was causing blank page after enabling compilation
    • Deleted Mage_Sales_Model_Recurring_Profile_Info, which was not on its place and added accidentally
    • Category and product design settings inheritance logic
    • Refactored one routine in Inventory Observer to remove code duplication
    • Disabling product attribute usage in promo rules not affect existing promo rules
    • Refactoring validation states for Centinel * Added template method Mage_Centinel_Model_StateAbstract::isLookupSuccessful
    • Add boolean type for catalog price rules and condition for category_ids
    • Removed Maestro/Switch/Solo card from system. Added Maestro/Switch and Solo cards to Chronopay and Cybersource methods
    • Mage_Adminhtml_Block_Sales_Order_Creditmemo block had dependence from ‘canCapture’ ‘canCapturePartial’. It was changed to ‘canRefund’ ‘canRefundPartialPerInvoice’. For set result of Mage_Adminhtml_Block_Sales_Items_Abstract::CanEditQty`s we can use setCanEditQty
    • Added Maestro/Switch and Solo Dollars card types for paypal_direct payment method. Also removed Maestro/Solo/Switch card type for this method
    • Removed “Shipping address” block on recurring profile view page if product is virtual. Also fixed virtual order detection
    • Refactored PayPal cart line items and cart totals calculation to accommodate various discounts and tax settings * added hidden discount and hidden shipping taxes to the calculation * eliminated cart line items logic from the helper, moved it to the paypal/cart model * simplified transferring of the totals and line items to PayPal API objects
    • Refactored sales rule discount detection on “buy_x_get_y” rule type
    • Added catalog_product table definition to product review collection
    • Changed type of obscure input field to ‘password’, so this field is hidden even when user enters data in it
    • Removed dependence to payment method on getting billing agreement method title. For now payment method title stored in billing agreement
    • Removed invoice creation thought zero subtotal checkout with new order status “pending”
    • Removed SID from url generation when Use SID on Frontend option is disabled
    • Added customer session validation for loadCustomerQuote method
    • Iphone clears.css has been deleted

    Fixes

    • Fixed Opening bestseller product (admin/dashboards) results in adding new product * fixed case when dashboard shows report for non-existing product (i.e. deleted one)
    • Fixed Bestsellers statistic bug * removed NULL values from statistic tables and changed foreign keys to cascade deleting stats for deleted products
    • Fixed Gift message displaying conditions not properly work on frontend and backend
    • Fixed QTY of product is incorrectly showed in Customer’s Current Activities - Shopping Cart and Customer’s Shopping Cart.
    • Fixed Gift message displaying conditions not properly work on frontend and backend - fixed missed bracked
    • Fixed Magento Connect Manager -> No warning message
    • Fixed Unable to upload community extention in Magento Connect Manager without Community Channel installed
    • Fixed Bundle product price calculated not correctly
    • Fixed Customer’s email doesn’t escalate to billing/shipping addresses * added copying email field from quote address to order address * added sending email to PayPal, when user’s address doesn’t contain email info
    • Fixed Catalog-specific attribute options do not load when using through catalog/output helper * method _getLoadDataFields at product attribute resource collection modified to select additional needed fields;
    • Fixed saving attribute value in store view scope only
    • Fixed Not searchable attributes are searched by Quick search.
    • Fixed Customers won’t appear in the search results on the customer grid in the admin
    • Fixed Huge memory consumption on flat shipping rates import * decrease to 5000 count of data wich inserts into DB in one iterate, to avoid exceed of 128M memory_limit
    • Fixed Config fields “Disable output” doesn’t implement inherited value
    • Fixed Category created for some store view not displayed on frontend * include_in_menu attribute was made as required to set default value when category created in specified store
    • Fixed creating of “Shopping Cart Price Rule’ * setActualProductAttributes method was called with ‘attribute_set_id’ value in $attributes param. But it does not exist in ‘eav/attribute’ table. So we need to check it
    • Fixed PayPal PE transaction_id detection: Overrided getPaypalTransactionId method in PE API - changed transaction id getting to process payflow accounts not assigned to paypal side
    • Fixed Configurable Product Catalog Price Rule Issue: the main idea is to calculate price rule on configurable price separately from base price
    • Fixed fatal error during import large file
    • Fixed Shipping information is not displayed in backend after Google Checkout operations
    • Fixed Field Mapping Issue during customer import
    • Fixed CMS blocks grid inoperable with store filter in GWS-limited mode
    • Fixed incorrect qty increment behaviour * qty increment not decimal validate * when adding product with qty increment to cart - redirect to product’s page * generate message about mismatch of qty increment when editing item qty at cart
    • Fixed ups/usps and Guam
    • Fidex issues with attaching product to multiple stores: refresh product index query update
    • Fixed displaying of bundle product weight
    • Fixed “Select a PayPal Solution” checkbox bug: Website Payments Pro and Website Payments Pro Payflow Edition consider each other status in their checkboxes control logic
    • Fixed Invoice Comments Stripped When Quantities Updated
    • Fixed XSS security issue on frontend
    • Fixed Google Chekout: Discount for shipping amount doesn’t apply
    • Fixed XSS issue in address form
    • Fixed Address in the customers address book cannot be deleted
    • Fixed CatalogSearch_Fulltext not being renewed for configurable products when editing attached simple products
    • Fixed Google Checkout: shipping method info is empty at order page in admin backend
    • Fixed Google Checkout: with discounted shipping - discount is applied again
    • Fixed Wrong timezone/DST in reports
    • Fixed coupon_code attribute inconsistency in some upgrade paths (from 1.4.0.0 to 1.4.1.0)
    • Fixed Created extension archive through Magento Connect include “.svn” directories
    • Fixed version of downloader
    • Fixed Magento Connect: User should has a possibility to choose version for extension upgrade
    • Fixed Magento Connect: User shouldn’t be able to download Magento into “0000 permissions” folders
    • Fixed Magento Connect: JS validation is absent for “Authors” tab on package extensions page
    • Fixed Magento Connect: Saving information on settings page
    • Fixed Magento Connect: “Configuration” step - server validation is absent during installation
    • Fixed Magento Connect: “Log in” page - Message or some information about required fields doesn’t appeared
    • Fixed Magento Connect: “Configuration” step - incorrect message appeared during installation
    • Fixed wrong shipping price in case of sales rule with fixed cart discount and 1 item in cart
    • Fixed the label for the configurable product attribute does not reflect correctly on the frontend
    • Fixed sales rule with fixed discount for whole cart doesn’t work
    • Fixed “Slash for category or product urls causes error 404”
    • Fixed Shared shopping cart on the stores with different domains * check origin url in all store urls * prevent to getting SID param from current query
    • Fixed #18454: Import profiles do not reset websites values
    • Fixed Issue with zero grand total express checkout for recurring products.
    • Fixed “Allow Gift message” setting on the product page doesn’t work in Front.
    • Fixed “Duplicate” of bundle product leads to an error
    • Fixed Catalog sitemap for categories shows inactive sub categories if flat catalog enabled
    • Fixed Added support of all product attributes in conditions/actions of salesRules.
    • Fixed Disabling product attribute usage in promo rules not affect existing promo rules
    • Fixed “Cart Price Rule not working with Product Attributes” (boolean values not properly shown in rule conditions)
    • Fixed Wrong amounts invoiced with FPT
    • Fixed Wrong order status after refund and additional related issue on frontend during checkout
    • Fixed Unable to delete uploaded sample for downloadable product
    • Fixed Paypal Direct send wrong billing address to API
    • Fixed Incorrect viewing of category settings after refreshing page
    • Fixed Catalog price rule discount not working during backend order creation
    • Fixed Double headers for session cookie set
    • Fixed Custom design is not reset properly after shipment comment emails
    • Fixed Tax report displays incorrect figures
    • Fixed Removed invoice creation on “completed” IPN message with payment_entity = “auth” to prevent double capture creation on single transaction with IPR.
    • Fixed Image browser in WYSIWYG editor doesn’t fill mouse over/out fields
    • Fixed Added rounding to “Refund Shipping” field on credit memo creation page.
    • Fixed Added additional error messages to customer address validation on PHP side while creating.
    • Fixed “No server side check for password length when customer edits his account information” * Also added proper processing for password == ‘0’, earlier it was considered as non-set password
    • Fixed WYSIWYG editor breaks directives that are not in src attribute
    • fixed directives decoding for a case when the secret key is present in URLs
    • Fixed Duplicate of a product creates it with no SKU value and is saved
    • Fixed Redundant catalog product attribute “category_ids” remains during upgrade from 1.3 to 1.4
    • Fixed Reports/Shopping cart/Products in carts optimization
    • Fixed “If all Storeviews value set up - disabled --> Front end shows default storeview instead of 404 page”
    • Fixed Added error on zero subtotal checkout with paypal express. Removed paypal express button on shopping cart with zero grand total.
    • Fixed Field labels and field values are not aligned vertically on Sales Orders in Admin
    • Fixed Spacing between field labels and field values is inappropriate on the Recurring Profiles tab in My Account section
    • Fixed Not searchable attributes are searched by Quick search. * Checking if attribute used in quick search before adding to fulltext field
    • Fixed Mage_Customer_Model_Customer::getGroupId can’t return zero value
    • Fixed #23184: Huge memory consumption on flat shipping rates import
    • Optimized and refactored Table Rate import
    • Fixed Scrolling during category load results in some js-errors
    • Fixed “Javascript alert on “manage category” page”
    • Fixed Security Vulnerability on Mage_Core_Block_Template level
    • Fixed Merged CSS breaks Secure Pages (https)
    • Fixed SOAP webservices do not work when enabling “Add Store Code to URLs”
    • Fixed Incorrect displaying of the Start Date entered by customer while adding to the cart recurring product
    • Fixed Downloadable Product “lable” typo
    • Fixed While creating gift message from backend it disappears in case of refreshing page
    • Fixed Product export fails when the quantity of exported products is 25 000 or more (memory leak in products)
    • Fixed While creating gift message from backend it disappears in case of refreshing page
    • Fixed Google Chekout: Discount for shipping amount doesn’t apply * onepage checkout recalculates shipping charges after setting the payment method (not solved yet in multishipping) * added warning about Carrier Calculated Shipping in Google Checkout system configuration * GC API callback now sets the payment method to quote on requests * the free shipping calculator now marks the entire address as “free shipping” if all its items have free shipping
    • Fixed On wide monitors checkbox “Create Permanent redirect” in admin backend wraps up to the end of input box
    • Fixed Tag isn’t showed in Product Page and My account->My Tags, if tag are deleted by customer, approved by administrator, added by customer
    • Fixed Non standard images make troubles with “Next"/"Previous" buttons
    • Fixed There is no validation of the Tracking number field during first time creation of the shipment
    • Fixed Missed dollar sign in variable name
    • Fixed Incorrect escaping of Mage_Catalog_Model_Abstract::loadByAttribute method * Zend_DB_Select::where must get null values to skip quoting into $cond empty strings if value is null
    • Fixed “URL rewrites duplicating when assigning to root category”
    • Fixed Shipping method UPS_XML missing titles
    • Fixed The pager is missing for tagged product list
    • Fixed Report > Products Ordered ignores Store view switcher
    • Fixed Flat catalog index problem after upgrade with customizations present
    • Fixed Incorrect bundle items inventory decrements
    • Fixed Category and product design settings inheritance
    • Fixed Removed fatal error on removing non existent quote item from quote
    • Fixed Credit Card Maestro/Solo: The field “Start Date” is not displayed on order information page * deleted unused Maestro/Solo from Payment module config * moved Maestro/Switch and Solo card definition from Chronopay to Payment module config * deleted Meastro/Switch definition with incorrect code MS from Cybersource module config * fixed logic of showing “Issue number” and “Start Date” of Switch/Solo card on frontend
    • Added warning about offline refund
    • Fixed Mage_Checkout_Block_Cart_Item_Renderer::getIsInStock bug
    • Fixed Fatal on edit configurable product page, if custom required price attribute is used
    • Fixed #0011135: View invoice error with changed query string
    • Fixed Trailing semi-colon displayed on Profile Export page
    • Fixed New Orders & Other Authenticated RSS feeds should use HTTPS
    • Fixed Dataflow export products sku filter works as not “starts with”, but “like”
    • Fixed Removed default shipping address assign on paypal express checkout
    • Fixed The customers from Puerto Rico can’t pay with PayPal (Express Checkout in PaypalUk)
    • Fixed Shared shopping cart on the stores with different domains
    • Fixed Discount amount for the whole cart divide proportionally between all affected items according to their base price and then applied.
    • Fixed Removed store selector in single store mode on url rewrite edit page
    • Fixed Javascript validator’s translation strings missing
    • Fixed Quick Search Autocomplete does not work via ajax http protocol for https page
    • Fixed Inventory->Qty Increments - unable to add
    • Fixed Loading search query performance issue
    • Fixed Changed labels in checkout and payment information blocs for credit cards Solo Maestro Switch
    • Fixed Product q-ty doesnt decrease after google checkout * added same ‘checkout_submit_all_after’ event to AmazonPayments * removed ‘TODO’ notice from Multishipping Checkout, because current scheme is better and will not be influenced by any Multishipping refactoring * fixed Observer reaction on ‘checkout_submit_all_after’ to include needed reindexing
    • Added checkout_multishipping_controller_success_action and checkout_onepage_controller_success_action events that pass the created order ids on frontend checkout success actions
    • Fixed Google Analytics tracking pages with wrong URI: * Completely reimplemented googleanalytics/ga block: * it doesn’t depend on session/quote, but just uses order_ids, if passed * the page_name parameter is reimplemented as it was intended to be: an optional parameter that can be customized via layout for certain actions * moved out the integration part with google checkout to observer * eCommerce tracking passes shipping address instead of the billing address, if available * replaced the “affiliation” into store frontend name in eCommerce tracking (as it is intended to be) * eliminated passing order item “category” in eCommerce tracking (that never existed) * optimized javascript code of GA with Google Checkout integration * Eliminated mutual code coupling between Google Analytics and Google Checkout modules * Improved integration of Google Analytics and Google Checkout: * the GA integration should appear only when GC buttons are available * there will be no integration when there is no GA tracking code configured * the GA/GC integration seems like wasn’t working because there was no pageTracker js variable accessible to the GC scripts
    • Fixed Wrong links in backend to “New Products/Low Stock/Customer reviews” RSS feeds
    • Fixed “Send auto-generated password” generates e-mail with incorrect template
    • Fixed Unable to refund Credit Memo because of Shipping Rounding
    • Fixed Added custom option info to recurring profile info page on frontend and backend.
    • Fixed Product Visibility and Status disappear when in search
    • Fixed Removed validation of new customer shipping address on backend for orders with virtual products only
    • Fixed ability to buy Product which have status “Out of Stock” through a direct link on button “Checkout with PayPal”
    • Fixed All free shipping methods in absent in Transfer Shipping Options menu on PayPal side
    • Fixed Payment methods titles for the PDF prints through admin gets from default config instead of the storeview config
    • Fixed PayPal and Puerto Rico shipping address
    • Fixed “Transfer Shipping Options” pass on PayPal side not correct value for Flat Rate method
    • Fixed Centinel JCB validation test cases 8-9
    • Fixed Saving caterory in store view scope
    • Fixed Attribute upgrades moved from 1.4.0.0.15 to 1.4.0.0.33
    • Fixed that product tagged by administrator has wrong URL at front-end
    • Fixed refusal from Card Verification (through link Exit), does not allow to place order repeatedly * If lookup was filed and customer tries again we will do new lookup. * If lookup was success and customer tries again without some changes we will not do new lookup * If authentication was filed and customer tries again we will do new lookup and authentication * If authentication was success and customer tries again without some changes we will not do new lookup and authentication
    • Fixed #22536: Light-weight email templates. Wishlist share email fix
    • Fixed declaration of Mage_Cybersource_Model_Api_ExtendedSoapClient::__doRequest() compatibility with SoapClient::__doRequest()
    • Fixed Two registration emails from a wrong store and without a logo are sent when a customer is created in Admin panel
    • Fixed Reindex for bundle products with date fields
    • Fixed Status is “Ready” instead to be “Reindex required” then creating new subcategory in mode “Manual Update” * index status changed to STATUS_REQUIRE_REINDEX when search engine changes
    • Fixed #23321: Wrong type casting in method
    • Fixed Print-All Includes Tracking # from All Shipments on Every Shipment
    • Fixed Ignored ‘Include in Navigation Menu’ category option with enabled flat catalog.
    • Fixed Admin unable to add Image through WYSIWYG to description and Short description without intermediate product saving
    • Fixed QTY decrement after multishipping
    • Double clicking adds product to cart twice
    • Fixed Catalog Price Rule(for NOT LOGGEN IN customers) is not applied for shopping cart and while checkout as guest or while first registration.
    • Fixed Payment methods titles for the PDF prints through admin gets from default config instead of the storeview config
    • Fixed Mage_Adminhtml_Model_System_Config_Backend_Serialized::_afterLoad() does not check input for unserialize()
    • Fixed Sending letters through “Contact Us” form, leads to error
    • Fixed PayPal Express with Flat Rate: incorrect counting Shipping amounts per order
    • Fixed Saving attribute value in store view scope only causes data loss.
    • Fixed #22607: Dispose of Mage_GiftRegistry module
    • Fixed Related products are not saved when you attach them to a product
    • Fixed Added qty to bundle unit price calculation to quote totals recalculating.
    • Fixed Saving category cause: ‘Exception’ with message ‘File was not uploaded.’ in /home/vadim.kusakin/dev/qa/2759/lib/Varien/File/Uploader.php:139
    • Fixed Fixed MAGE-638 Magento Connect -> MCM -> If agreement checkbox is unchecked, “Continue” button should be disabled
    • Fixed Set the same column font size as in cells in PDF documents printing
    • Fixed Home page appears instead of predefined 404 page
    • Fixed Removed converting of “is one of” and “is not one of” values in decimal.
    • Fixed Wrong column type for order_increment_id on Invoice, Shipments, Creditmemo grids * order_increment_id was setted as “text” instead of “number” type
    • Fixed Inconsistency with credit memos showing buttons online vs offline
    • Fixed PayPal Express shortcut is missed on product page
    • Fixed An email is sent to a customer after its profile is edited in the Admin panel
    • Fixed that Payflow Pro includes only the first line of billing/shipping addresses into request
    • Fixed Incorrect showing of product page when inputing a product description with table which have attribute align = left
    • Fixed Wrong link for bestsellers in admin dashboard. Grids.php fixture doesn’t do anything for this bug - just to beautify code.
    • Fixed Added fixes to reports - base_discount_amount is actually kept negative in DB.
    • Fixed Empty dropdown ‘status’ at the creation New Review Grid.
    • Fixed Incorrect work of “Recently Compared Products” functional on category’s page
    • Fixed behavior when having single store, javascript raises exception and all followed code is not executed
    • Fixed that Special price for dynamic bundle applies twice
    • Fixed #21960: Labels in page/html_wrapper and core/text_list in layout
    • Fixed GUI bugs on Recurrent Profile frontend part
    • Fixed Magento Connect -> Message about invalid URL is duplicated
    • Fixed that suspend Recurring Profile from front side leads to error
    • Fixed Missing pager for tagged product list
    • Fixed Wrong profiler output for getUrl in Category
    • Fixed Saving of billing agreement relation with order - added force billing agreement re-saving and fixed isValid method in agreement detection.
    • Fixed Incorrect sort order reliable on mysql internal order during eav attribute load * move prepare select to separate method
    • Fixed passing additional totals to PayPal when cart line items are disabled: * simplified paypal/abstract api to just set the paypal/cart instance and the needed configuration settings * moved workarounds of setting shipping and discount totals as line items into the appropriate APIs: WPS and NVP
    • Fixed In My product Review short description HTML tags are shown
    • Fixed that Refund from google chekout don’t display on the order in Magento
    • Fixed that “Compare Products” block does not appear on the category page and product page
    • Fixed Non-existing attribute’s source model causes fatal error
    • Fixed Varien_Db_Select memory leak
    • Fixed #18569: Gift Messages not in OrderInfo returned array
    • Fixed PayPal API credentials wizard popup size
    • Fixed #11449: customer_id is mismatch with entity_id in customer.create
    • Fixed merging CSS-files with different skin domain to pick a proper base URL
    • Fixed Bad UI style on checkout success page
    • Fixed buying more than 1 virtual product in multishipping checkout
    • Fixed #22518: Wrong amount for second refund
    • Fixed #22776: Bug Causing Recursion Error
    • Fixed #22668: Incorrect reports for coupons
    • Fixed Products -> Product with “Out of stock” status displayed on frontend, but shouldn’t
    • Fixed Password miss match for newly created in Back end customer
    • Fixed “There has been an error processing your request” page is displayed when specified order status is selected on Reports->Sales->Tax page
    • Fixed bug with ‘Use Flat Catalog Category’
    • Fixed #13770, #16300, #21040 : Product Media Api Broken, product_media.create API overwrites image itself each upload, product_media.update API does not upgrade the image itself
    • Fixed #16306: Webservice with htaccess (changes in code style)
    • Fixed #22536: Light-weight email templates
    • Fixed #18935: Soap api v2 multiple complexFilters with the same key
    • Fixed incorrect Window titles on frontend
    • Fixed Eliminated display currency usage (instead of the base website currency) in shopping cart price rule conditions
    • Fixed #21146: Magento falls into the white screen when saving URL rewrite for a product on the Default Store View * corrected syntax mistakes
    • Fixed batch of issues related to google checkout: * Invoice don’t create automatically with Google Checkout * Google checkout invoice duplication * Automatically authorize the buyer’s credit card for the full amount of the order * Refund from google checkout don’t display on the order in Magento * Google Chekout: Discount for shipping amount doesn’t apply * Different order amount in Google checkout and Magento orders * Applying of discount for shipping, when using google checkout * Order is in google sandbox doesn’t contain gift card
    • Fixed #23461: Wrong attribute value in catalog link widget XML
    • Fixed getting complete state for orders with zero grand total when processed
    • Added Store id param to billing agreement entity. Also fixed store setting in billing agreement payment method.
    • Fixed fatal error in payment method list fetching (MAGE-500)
    • Fixed #22575: Trace error during using filter “Products” on Tags page
    • Fixed Grids with settings remain active while disabled PayPal methods
    • Fixed configuration merger fatal error when store/website resource structure is inconsistent
    • Fixed PayPal admin setup: checkbox problem
    • Fixed Adding shipping address transferring on non guest checkout in Paypal Standard
    • Fixed “Save in address book” checkbox in the Shipping address area doesn’t work while admin order creation
    • Fixed pre-selecting default address during checkout
    • Fixed Email with empty password is sent to a customer after an order is created in the Admin panel
    • Fixed Necessary to add data validation for filed “Trial Billing Frequency” in Recurring Profile
    • Fixed “Out of Stock” product is possible to purchase successfully through Shortcut button
    • Fixed phpdocs in lib/Varien and removed junk file
    • Fixed #21146: Magento falls into the white screen when saving URL rewrite for a product on the Default Store View
    • Fixed #21643: Fixed “wsdl” parameter validation for Soap V2 * Changed class SoapServer with class Zend_Soap_server * Added ability to set response charset from admin panel: System->Configuration->Magento Core API
    • Fixed #21499: Default billing and shipping address
    • Fixed #21565: missing “comment” for salesOrderStatusHistoryEntity
    • Fixed #20481: Access Control List not retrieved for API user for resources() and resourceFaults() operations
    • Fixed #18367: FCGI Error on WSDL Url with Apache and mod_fastcgi
    • Fixed #22053: use HTTP 301 code instead of 302 in case of web/url/redirect_to_base
    • Fixed #20654: Admin order creation->Move mouse cursor isn’t changed into hand while move it on some product for adding
    • Fixed #21590: Attribute ‘Date’: testing for uniqueness fields not working
    • Fixed #21566: Type of attribute ‘Price’: Possible to add text value for field ‘default value’
    • Fixed #22053: added optional behavior (301 or 302)
    • Fixed #21570: Review from not logged in user is saved in list of All Reviews when “Allow guests to write reviews = No”
    • Fixed #22090: Different values of Qty Increments during create and after duplicate products
    • Fixed #22489: Eliminate difference between bundle.js in different skins
    • Fixed #22419: Set default stock_data if not exist in create/update product
    • Fixed #20227: “Review(x)” link should be added to the compare page.
    • Fixed #21570: Review from not logged in user is saved in list of All Reviews when “Allow guests to write reviews = No”
    • Fixed #20959: Locale problem in shipping tracking popup raises exception
    • Fixed #21955: Layout cache ignores product column count update
    • Fixed #20011: After using filter “Color” or “Manufacture” in Configurable Product meaning from column is disappear
    • Fixed #21908: Incorrect attribute ordering in “Compare products” page.
    • Fixed #22222: Edit review-> if browse stores in the “Visible In “ drop-down, rating values reseted
    • Fixed #22075: Product Attribute title specified for StoreView isn’t showing on the configurable product’s page
    • Fixed #22605: catalog_category.level return root categories when website or store are null
    • Fixed #21806: Different values display on the shopping cart in front-end and back-end
    • Fixed #20113: Shipping address display as default on the front-end and as not default on admin for one customer
    • Fixed #22575: Trace error during using filter “Products” on Tags page * added ‘filter_index’ to array parameter in addColumn() method call
    • Fixed #14591: Incorrect SKU for Configurable Product with Custom Options
    • Fixed #22476: Blank Column in Related Products Grid * deleted duplicate output for editable columns
    • Fixed #22575: Trace error during using filter “Products” on Tags page * apply filter_index field values to index
    • Fixed #22644: A discrepancy between GT(Base) and GT(Purchased)
    • Fixed #22645: Incorrect original price when using custom price in order.
    • Fixed #22653: Missed checking for file existence in JS/CSS merger * checking in source file exists. If not - do not check last modification and force to merge target file again
    • Fixed #22594: Unable to place orders through checkout with multiple addresses with PayPal direct + zero subtotal for one order
    • Fixed #21185: Newsletter confirmed automatically BEFORE account email is confirmed.
    • Fixed #22167: “Add new row” button in downloadable product
    • Fixed #21952: BUG - Category / Url Model (UYN-886991)
    • Fixed #15334, #17794 * API category did not pass validation process due to available_sort_by must be ArrayOfString * Added category validation for backend (missed) * Creating separate validation for available_sort_by and default_sort_by attributes
    • Fixed #22599 Upgrade from 1.1.8 to 1.8.0.0 database compatibility issues (PARTIAL)
    • Fixed #22661: 1 cent bug
    • Fixed #22434: 100% discount of products -> the amounts of Tax and Grand Totals are or negative or not corectly
    • Fixed #10073: Unnecessary option for downloadable products
    • Fixed #20014: Qty use decimals for downloadable
    • Fixed #22164: Incorrect message for maximum shipping amount
    • Fixed #22174: Custom ‘Qty to Refund’ isn’t remembered after message about incorrect amount
    • Fixed #22182: The value of ‘Customer Since’ field to duplicate clients at different sites.
    • Fixed #22243: Add new review by admin->type of this review is ‘guest’, but should be ‘administrator’
    • Fixed #22313: Time of order creation if not displayed by the “Order Created At (datetime)” template variable.
    • Fixed #22348: “Add to card” button is absent for giftcard product in the catalog
    • Fixed #22640: Creating customer unable after adress tab manipulations
    • Fixed #22670: Credit memo - incorrect shipping price displaying
    • Fixed #22798: Excl and Inc. Tax don’t display on the Estimate Shipping and Tax block
    • Fixed #20088: Admin able to push on-line refund button for the capture off-line invoice
    • Fixed #16306: Webservice with htaccess. Added server authorization (.htaccess)
    • Fixed #22266: HEADERS ALREADY SENT Error during dataflow import * Additionally: moveing layout update in separate layout file of dataflow module.
    • Fixed #21412: The “Save Attribute” and “Save and Continue Edit” buttons become disabled after saving attribute with attribute code that exists
    • Fixed #22844: After login to admin got 404 instead Startup Page
    • Fixed #22852: shopping cart price rule - search by ID - error page
    • Fixed #15897: Unsubscription Email Sender in the Newsletters Subscription Options is not working correctly
    • Fixed #15899: Newsletters subscription confirmation in not working
    • Fixed #22908: Grid Serializer doesn’t handle dropdowns as edit columns
    • Fixed #22946: ‘Products Tagged by Administrators’ grid contains information about product that is assigned by the customer
    • Fixed #22935: Issue with Google AdWords and DSMM Code
    • Fixed #22910: view of system/design table with no records under IE 8
    • Fixed #22914: view of URL rewrite table with no records under IE 8
    • Fixed #22935: Issue with Google AdWords and DSMM Code
    • Fixed #22536: Light-weight email templates
    • Fixed #23017: Memcache session fallback does not work
    • Fixed #22992: Trace appears during create reorder from front-end
    • Fixed #22991: Cannot add items to shopping cart after active ‘Use Flat Catalog Product’
    • Fixed #22813: Google base Undefined Offset when Managing attribute mapping
    • Fixed #23138: URL rewrite error on product creation
    • Added Regions for baltic states and Finland
    • Fixed #23092: Memcached and compiler
    • Fixed #19804: sorting/searching by “inventory” field
    • Fixed #23241: Catalog price rule not correctly appy for customer group
    • Fixed #16294: WSDL missing attributes for customerCustomerEntity
    • Fixed #22851: Used wrong resource model for api/user
    • Fixed #18207: SOAP-ERROR: Parsing Schema: can’t import schema from ‘http://schemas.xmlsoap.org/soap/encoding/’
    • Fixed Fatal error: Call to undefined function eaccelerator_fetch()

  • Joomla! 1.5.3 Released

    7 year(s) ago

    The Joomla! community is pleased to announce the immediate availability of Joomla! 1.5.3 [Vahi]. This release is earlier than scheduled in order to correct a database name validation error introduced in 1.5.2. It has been a month since Joomla! 1.5.2 was released on March 23, 2008. The goal is to provide regular, frequent updates to the Joomla! end user community containing the latest bug fixes and minor enhancements.

    Instructions

    Download Joomla! 1.5.3 and update packages

    Want to test drive Joomla!? Try the online demo. Documentation is available for beginners.

    Release Notes

    • Database name validation
    • xHTML compliance fixes
    • Help screen updates
    • JFilterInput infinite loop fix
    • PDF fixes for PHP 4
    • Minor CSS and RTL issues

    Statistics

    Sincere thanks to the Joomla! Bug Squad for their dedicated efforts investigating reports, fixing problems, and applying patches to Joomla!. If you find a bug with Joomla!, please report the bug using the Joomla! tracker.

    Statistics for the 1.5.3 release period:

    • The 1.5.3 release period was 4 weeks and 3 days, 8 committers, 32 commits and 192 file changes.
    • 109 issues closed with an average open period of 21 days.
    • 173 issues remain open, 46% (85) were reported during this last period.
    • 1.5.3 is released at Revision 10,224.
    • 45 installation languages are available.

    Members of the Bug Squad, include: Anthony Ferrara (lead), Akarwuth Tamrareang, Ahmad Alfy, Akash Mehta, Andrew Eddie, Bruce Scherzinger, Elin Waring, Ercan Ozkaya, Hannes Pappenberg, Ian MacLennan, Jennifer Marriott, Jens-Christian Skibakk, Joseph LeBlanc, Justo de Rivera, Kevin Devine, Mati Kochen, Michael Casha, Pieter J. van Horssen, Samuel Moffatt, Shantanu Bala, Toby Patterson, Tomasz Dobrzynski, and Wilco Jansen.

    Warm welcome to the newest members of the Bug Squad: Danh Le Phuoc, Isaac Shabtay, Jay Kendall, Jerry Hilburn, and Phillip Richdale.

    Joomla! 1.5.4 goals

    • Profiling and performance optimization
    • Plugin refactoring and introduction of unit testing (see Unit Testing current status and background info)
    • Complete remaining translation issues
    • Continue working on the //TODO tags in source code
    • Update of the OpenID library to 2.0

  • 如何让网页字体更美观,利用 CSS 字体模块(Font Module) Level 3

    7 year(s) ago

    http://www.w3.org/TR/2009/WD-css3-fonts-20090618/
    这个地址是w3c的css3 字体文档。
    
    我们将关键部分节选下来,可以导入google字体或者其他优秀的中文字体库来提高中文字体在页面的显示效果:
    4 Font resources
    4.1 The @font-face rule
    
    The @font-face rule allows for linking to fonts that are automatically activated when needed. This permits authors to work around the limitation of "web-safe" fonts, allowing for consistent rendering independent of the fonts available in a given user's environment. A set of font descriptors define the location of a font resource, either locally or externally, and the style characteristics of an individual face. Multiple @font-face rules can be used to construct font families with a variety of faces. Using CSS font matching rules, a user agent can selectively download only those faces that are needed for a given piece of text.
    
    The general form of an @font-face at-rule is:
    
    @font-face {  }
    
    where  has the form:
    
    descriptor: value;
    descriptor: value;
    [...]
    descriptor: value;
    
    Each @font-face rule specifies a value for every font descriptor, either implicitly or explicitly. Those not given explicit values in the rule take the initial value listed with each descriptor in this specification. These descriptors apply solely within the context of the @font-face rule in which they are defined, and do not apply to document language elements. There is no notion of which elements the descriptors apply to or whether the values are inherited by child elements. When a given descriptor occurs multiple times in a given @font-face rule, only the last specified value is used, all prior values for that descriptor are ignored.
    
    To use a downloadable font called Gentium:
    
    @font-face {
      font-family: Gentium;
      src: url(http://site/fonts/Gentium.ttf);
    }
    
    p { font-family: Gentium, serif; }
    
    The user agent will download Gentium and use it when rendering text within paragraph elements. If for some reason the site serving the font is unavailable, the default serif font will be used.
    
    A given set of @font-face rules define a set of fonts available to containing documents. Multiple rules can be used to define a family with a large set of faces. When font matching is done fonts defined using these rules are considered before other available fonts on a system.
    
    Downloaded fonts are only available to documents that reference them, they should not be made available to other applications or other documents. User agent implementors might consider it convenient to use downloaded fonts when rendering characters in other documents for which no other available font exists as part of the system font fallback procedure. This however leads to non-deterministic rendering patterns where the appearance of a page effectively becomes a function of browsing history.
    
    User agents which do not understand the @font-face rule encounter the opening curly bracket and ignore forward until the closing curly bracket. This at-rule conforms with the forward-compatible parsing requirement of CSS, parsers may ignore these rules without error. Any descriptors that are not recognized or implemented by a given user agent must be ignored. @font-face rules require a font-family and src descriptor, if either of these are missing the @font-face should be ignored.
    
    In cases where user agents have limited platform resources or implement the ability to disable downloadable font resources, @font-face rules should simply be ignored; the behavior of individual descriptors as defined in this specification should not be altered.
    4.2 Font family: the ‘font-family’ descriptor
    Name: 	font-family
    Value: 	
    Initial: 	N/A
    
    This descriptor defines the font family name that will be used in all CSS font family name matching, overriding font family names contained in the underlying font data. If the font family name is the same as a font family available in a given user's environment, it effectively hides the underlying font for documents that use the stylesheet. This permits a web author to freely choose font-family names without worrying about conflicts with font family names present in a given user's environment. Errors loading font data do not affect font name matching behavior. User agents that apply platform font aliasing rules to font family names defined via @font-face rules are considered non-conformant.
    4.3 Font reference: the ‘src’ descriptor
    Name: 	src
    Value: 	[  [format( [, ]*)] |  ] [,  [format( [, ]*)] |  ]*
    Initial: 	N/A
    
    This descriptor specifies the resource containing font data. It is required, whether the font is downloadable or locally installed. It's value is a prioritized, comma-separated list of external references or locally installed font face names. When a font is needed the user agent iterates over the set of references listed, using the first one it can successfully activate. Fonts containing invalid data are treated as if they were not found, the user agent loads the next font in the list.
    
    External references consist of a URI, followed by an optional hint regarding the format of the font resource referenced by that URI. The format hint contains a comma-separated list of format strings that denote well-known font formats. Conformant user agents should skip downloading a font resource if the format hints indicate only unsupported or unknown font formats. If no format hints are supplied, the user agent should download the font resource.
    
    An initial list of format strings defined by this specification and representing formats likely to be used by implementations on various platforms is:
    String 	Font Format 	Common extensions
    "truetype" 	TrueType 	.ttf
    "opentype" 	OpenType 	.ttf, .otf
    "truetype-aat" 	TrueType with Apple Advanced Typography extensions 	.ttf
    "embedded-opentype" 	Embedded OpenType 	.eot
    "svg" 	SVG Font 	.svg, .svgz
    
    Given the overlap in common usage between TrueType and OpenType, for the purpose of a format hint "truetype" and "opentype" should be considered as synonymous; a format hint of "opentype" does not imply that the font contains Postscript CFF style glyph data or that it contains OpenType layout information (see Appendix A for more background on this). The "truetype-aat" string indicates that a font contains Apple Advanced Typography tables so user agents on platforms that do not support these tables should treat this format as unsupported. This allows authors to provide multiple fonts for rendering complex scripts such as Arabic or Devanagari that require platform-specific font data.
    
    Issue: does a public registry need to be established for these hints?
    
    A full font URI with no format hint:
    
      src: url(http://site/fonts/font.otf);
    
    Arabic font with different versions for specific platforms:
    
      src: url(../fonts/LateefRegAAT.ttf) format("truetype-aat"), 
           url(../fonts/LateefRegOT.ttf) format("opentype");
    
    A font containing tables to support multiple advanced font formats:
    
      src: url(DoulosSILR.ttf) format("opentype","truetype-aat");
    
    As with other URIs in CSS, the URI may be partial, in which case it is resolved relative to the location of the style sheet containing the @font-face rule. In the case of SVG fonts, the URL points to an element within a document containing SVG font definitions. If the element reference is omitted, a reference to the first defined font is implied.
    
    The locally installed  is a format-specific string that uniquely identifies a single font face within a larger family. For TrueType and OpenType fonts, the full font name as defined in the font name table is used to reference a given face. Additionally, for TrueType and OpenType fonts user agents may optionally support Postscript name lookup on platforms where that is appropriate. The notation for a  is the unique font face name enclosed by "local(" and ")". The name can optionally be enclosed in quotes. This also allows for referencing faces that belong to larger families that cannot otherwise be referenced. If a font face with a given full font name or Postscript name is not found, the user agent loads the next font in the list, platform substitutions for the font should not be used.
    
    Use the local copy of a font or download it if it's not:
    
    @font-face {
      font-family: Gentium;
      src: local(Gentium), url(/fonts/Gentium.ttf);
    }
    
    Use a local font or reference an SVG font in another document:
    
    @font-face {
      font-family: Headline;
      src: local(Futura-Medium), 
           url(fonts.svg#MyGeometricModern) format("svg");
    }
    
    Create an alias for local Japanese fonts on different platforms:
    
    @font-face {
      font-family: Japanese;
      src: local(HiraKakuPro-W3), local(Meiryo), local(IPAPGothic);
    }
    
    Reference a font face that cannot be matched within a larger family:
    
    @font-face {
      font-family: Hoefler Text Ornaments;
      /* has the same font properties as Hoefler Text Regular */
      src: local(HoeflerText-Ornaments); 
    }
    
    4.4 Font property descriptors: the ‘font-style’, ‘font-weight’, ‘font-stretch’ descriptors
    Name: 	font-style
    Value: 	normal | italic | oblique
    Initial: 	normal
    Name: 	font-weight
    Value: 	normal | bold | 100 | 200 | 300 | 400 | 500 | 600 | 700 | 800 | 900
    Initial: 	normal
    Name: 	font-stretch
    Value: 	normal | ultra-condensed | extra-condensed | condensed | semi-condensed | semi-expanded | expanded | extra-expanded | ultra-expanded
    Initial: 	normal
    
    These descriptors define the characteristics of a font face and are used in the process of matching styles to specific faces. For a font family defined with several @font-face rules, user agents can either download all faces in the family or use these descriptors to selectively download font faces that match actual styles used in document. The values for these descriptors are the same as those for the corresponding font properties except that relative keywords are not allowed: bolder, lighter, wider, narrower. If these descriptors are omitted, default values are assumed.
    
    The value for these font face style attributes is used in place of the style implied by the underlying font data. This allows authors to combine faces in flexible combinations, even in situations where the original font data was arranged differently. User agents that implement synthetic bolding and obliqueing should only apply synthetic styling in cases where the font descriptors imply this is needed, rather than based on the style attributes implied by the font data.
    4.5 Character range: the ‘unicode-range’ descriptor
    Name: 	unicode-range
    Value: 	 [, ]*
    Initial: 	U+0-10FFFF
    
    This descriptor defines the range of Unicode characters supported by a given font. The values of  are expressed using hexadecimal numbers prefixed by "U+", corresponding to Unicode character code points. The unicode-range descriptor serves as a hint for user agents when deciding whether or not to download a font resource.
    
    Unicode range values are written using hexadecimal values and are case insensitive. Each is prefixed by "U+" and multiple, discontinuous ranges are separated by commas. Whitespace before or after commas is ignored. Valid character code values vary between 0 and 10FFFF inclusive. A single range has three basic forms:
    
        * a single code point (e.g. U+416)
        * an interval value range (e.g. U+400-4ff)
        * a range where trailing ‘?’ characters imply ‘any digit value’ (e.g. U+4??) 
    
    Ranges that do not fit any of the above three forms are considered to be parse errors and the descriptor is omitted. Interval ranges consisting of a single code point are valid. Ranges specified with ‘?’ that lack an initial digit (e.g. "U+???") are also valid, and are treated as if there was a single 0 before the question marks (thus, "U+???" = "U+0???" = "U+0000-0FFF"). "U+??????" is not a syntax error, even though "U+0??????" would be. Ranges can overlap but interval ranges that descend (e.g. U+400-32f) are invalid and omitted rather than treated as parse errors; they have no effect on other ranges in a list of ranges. Ranges are clipped to the domain of Unicode code points (currently 0 - 10FFFF inclusive); a range entirely outside the domain is omitted. Without any valid ranges, the descriptor is omitted. User agents may normalize the list of ranges into a list that is different but represents the equivalent set of character code points.
    
    The character range can be a subset of the full character map of the underlying font. The effective unicode-range used when mapping characters to fonts is the intersection of the unicode range specified and the underlying character map of the font. This means that authors do not need to define the unicode-range of a font precisely, broad ranges for which a sparse set of code points are defined in the font can be used. Code points outside of the defined unicode-range are ignored, irregardless of whether the font contains a glyph for that code point or not. User agents that download fonts for characters outside the defined unicode-range are considered non-conformant. Likewise, user agents that render a character using a font resource for which the defined unicode-range does not include that character are also considered non-conformant.
    
    Example ranges for specific languages or characters:
    
    unicode-range: U+A5;
        a single code point, the yen/yuan symbol 
    unicode-range: U+0-7F;
        code range for basic ASCII characters 
    unicode-range: U+590-5ff;
        code range for Hebrew characters 
    unicode-range: U+A5, U+4E00-9FFF, U+30??, U+FF00-FF9F;
        code range for Japanese kanji, hiragana and katakana characters plus yen/yuan symbol 
    
    The BBC provides news services in a wide variety of languages, many that are not well supported across all platforms. Using an @font-face rule, the BBC could provide a font for any of these languages, as it already does via a manual font download.
    
    @font-face {
      font-family: BBCBengali;
      src: url(fonts/BBCBengali.ttf) format("opentype");
      unicode-range: U+00-FF, U+980-9FF;
    }
    
    Technical documents often require a wide range of symbols. The STIX Fonts project is one project aimed at providing fonts to support a wide range of technical typesetting in a standardized way. The example below shows the use of a font that provides glyphs for many of the mathematical and technical symbol ranges within Unicode:
    
    @font-face {
      font-family: STIXGeneral;
      src: local(STIXGeneral), url(/stixfonts/STIXGeneral.otf);
      unicode-range: U+000-49F, U+2000-27FF, U+2900-2BFF, U+1D400-1D7FF;
    }
    
    Multiple @font-face rules with different unicode ranges for the same family and style descriptor values can be used to create composite fonts that mix the glyphs from different fonts for different scripts. This can be used to combine fonts that only contain glyphs for a single script (e.g. Latin, Greek, Cyrillic) or it can be used by authors as a way of segmenting a font into fonts for commonly used characters and less frequently used characters. Since the user agent will only pull down the fonts it needs this helps reduce page bandwidth.
    
    If the unicode ranges overlap for a set of @font-face rules with the same family and style descriptor values, the rules are ordered in the reverse order they were defined; the last rule defined is the first to be checked for a given character.
    
    This example shows how an author can override the glyphs used for Latin characters in a Japanese font with glyphs from a different font. The first rule specifies no range so it defaults to the entire range. The range specified in the second rule overlaps but takes precedence because it is defined later.
    
    @font-face {
      font-family: JapaneseWithGentium;
      src: local(MSMincho);
      /* no range specified, defaults to entire range */
    }
    
    @font-face {
      font-family: JapaneseWithGentium;
      src: url(../fonts/Gentium.ttf);
      unicode-range: U+0-2FF;
    }
    
    Consider a family constructed to optimize bandwidth by separating out Latin, Japanese and other characters into different font files:
    
    /* fallback font - size: 4.5MB */
    @font-face {
      font-family: DroidSans;
      src: url(DroidSansFallback.ttf);
      /* no range specified, defaults to entire range */
    }
    
    /* Japanese glyphs - size: 1.2MB */
    @font-face {
      font-family: DroidSans;
      src: url(DroidSansJapanese.ttf);
      unicode-range: U+3000-9FFF, U+ff??;
    }
    
    /* Latin, Greek, Cyrillic along with some 
       punctuation and symbols - size: 190KB */
    @font-face {
      font-family: DroidSans;
      src: url(DroidSans.ttf);
      unicode-range: U+000-5FF, U+1e00-1fff, U+2000-2300;
    }
    
    For simple Latin text, only the font for Latin characters is downloaded:
    
    body { font-family: DroidSans; }
    
    

    This is that

    In this case the user agent first checks the unicode-range for the font containing Latin characters (DroidSans.ttf). Since all the characters above are in the range U+0-5FF, the user agent downloads the font and renders the text with that font. Next, consider text that makes use of an arrow character (⇨):

    This ⇨ that

    The user agent again first checks the unicode-range of the font containing Latin characters. Since U+2000-2300 includes the arrow code point (U+21E8), the user agent downloads the font. For this character however the Latin font does not have a matching glyph, so the effective unicode-range used for font matching excludes this code point. Next, the user agent evaluates the Japanese font. The unicode-range for the Japanese font, U+3000-9FFF and U+ff??, does not include U+21E8, so the user agent does not download the Japanese font. Next the fallback font is considered. The @font-face rule for the fallback font does not define unicode-range so it's value defaults to the range of all Unicode code points. The fallback font is downloaded and used to render the arrow character. 5 Font matching algorithm The procedure for choosing fonts consists of iterating over the font families determined by the font-family property, selecting a font face with the appropriate style based on other font properties and then determining whether a glyph exists for a given character. This procedure is performed on each character to be rendered. Optimizations are allowed provided that an implementation behaves as if the algorithm had been followed exactly. Matching occurs in a well-defined order to insure that the results are as consistent as possible across user agents, given an identical set of available fonts and rendering technology. To begin with, a user agent must determine the set of font families available on a given platform and determine the style characteristics of all faces for each family. If two faces have the exact same style characteristics, one of them is ignored. Fonts available via @font-face rules are referenced per document and are not treated as generally available fonts. 1. For each character within a given element, the user agent evaluates the font properties applicable. The user agent starts with the first family name in the ‘font-family’ prioritized list. 2. If the family name is a generic family name, the user agent looks up the appropriate font family name to be used. User agents may choose the generic font family to use based on the language of the containing element or the Unicode range of the character. The user agent attempts to find the family name among fonts defined via @font-face rules and then among available system fonts. 3. If a font family match occurs, the user agent then attempts to select a face that matches the remaining font properties. It matches these properties in the order given below: 1. ‘font-stretch’ is tried first. ‘normal’ matches a font not labeled as ‘condensed’ or ‘expanded’. 2. ‘font-style’ is tried next. ‘italic’ will be satisfied if there is either a face in the UA's font database labeled with the CSS keyword ‘italic’ (preferred) or ‘oblique’. Otherwise the values must be matched exactly or font-style will fail. 3. ‘font-variant’ is tried next. ‘normal’ matches a font not labeled as ‘small-caps’; ‘small-caps’ matches (1) a font labeled as ‘small-caps’, (2) a font in which the small caps are synthesized, or (3) a font where all lowercase letters are replaced by uppercase letters. A small-caps font may be synthesized by electronically scaling uppercase letters from a normal font. 4. ‘font-weight’ is matched next, it will never fail. If bolder/lighter relative weights are used, calculate the effective weight based on the inherited weight value, as described in the definition of font-weight above. Given the desired weight and the set of face weights that match the properties above, if the desired weight is available that face matches. Otherwise, a weight is chosen using the rules below: * If the desired weight is less than 400, weights below the desired weight are checked in descending order followed by weights above the desired weight in ascending order until a match is found. * If the desired weight is greater than 500, weights above the desired weight are checked in ascending order followed by weights below the desired weight in descending order until a match is found. * If the desired weight is 400, 500 is checked first and then the rule for desired weights less than 400 is used. * If the desired weight is 500, 400 is checked first and then the rule for desired weights less than 400 is used. 5. ‘font-size’ must be matched within a UA-dependent margin of tolerance. (Typically, sizes for scalable fonts are rounded to the nearest whole pixel, while the tolerance for bitmapped fonts could be as large as 20%.) Further computations, e.g., by ‘em’ values in other properties, are based on the ‘font-size’ value that is used, not the one that is specified. 4. If no matching face exists or the matched face does not contain a glyph for the character to be rendered, the next family name is selected and the previous two steps repeated. If the matched font is defined via an @font-face rule, the font resource is downloaded. Otherwise if the matched font is defined via @font-face and needs to be downloaded, the user agent can either wait until the font is downloaded or render once with substituted font metrics and render again once the font is downloaded. 5. If there are no more font families to be evaluated and no matching face has been found, then the user agent performs a system font fallback procedure to find the best match for the character to be rendered. The result of this procedure may vary across user agents. 6. If a particular character cannot be displayed using any font, the user agent should indicate by some means that a character is not being displayed, either by displaying a symbolic representation of the missing glyph or using the ‘missing character’ glyph from another font. It's useful to note that the CSS selector syntax may be used to create language-sensitive typography. For example, some Chinese and Japanese characters are unified to have the same Unicode code point, although the abstract glyphs are not the same in the two languages. *:lang(ja-jp) { font: 900 14pt/16pt "Heisei Mincho W9", serif; } *:lang(zh-tw) { font: 800 14pt/16.5pt "Li Sung", serif; } This selects any element that has the given language - Japanese or Traditional Chinese - and uses the appropriate font.

  • Magento中 OpenSearch 对电子商务的作用

    7 year(s) ago

    OpenSearch 在电子商务上可以更好的利用浏览器的搜索条,做到端对端的直接搜索,提高客户的粘性。
    
    其实际效果是添加工具条在Firefox这类浏览器上,实现客户直接站内搜索的效果。
    
    我们对 Magento 的OpenSearch模块开发正在进行中。实现后将会有效提高客户的查询效率,避免3次点击的客户体验效率降低。
    
    以下是OpenSearch的介绍:
    

    Introduction

    OpenSearch is a collection of simple formats for the sharing of search results. The OpenSearch description document format can be used to describe a search engine so that it can be used by search client applications. The OpenSearch response elements can be used to extend existing syndication formats, such as RSS and Atom, with the extra metadata needed to return search results.

    For everyone

    For developers

    Specifications

    Documentation

    Community

  • Magento 企业版1.9的新功能

    7 year(s) ago

    Gift Registry

    Customer Attribute Management

    Full Page Caching – New Enhancements

    Solr Search – New Enhancements

    Magento Connect for Magento Enterprise

    Magento Secure Payment Bridge (PA-DSS Compliant)

    我们一个一个来分析关键的功能部分: 1 礼品部分添加的Registry更趋于西方的赠品模式 2 客户属性现在的后台支持更加自由,可以定义用户注册,用户属性显示等字段。管理自由,方便。 3 全页缓存。这部分的性能得到了进一步提高,具体数据我们将会之后提供。 4 Solr搜索的集成,整合了apache的solr项目,可以将搜索和数据挖掘结合起来,满足业务智能化。 除此以外,我们在实际项目研究中发现新的企业版本1.9还有一些特色功能,虽然没有被官方披露,但是方便了程序编码,有利于缩短程序代码和模块的开发。

  • Magento 的API适合做什么?

    7 year(s) ago

    一直以来我们都发现Magento很强大,很灵活。其中最为弹性的一个特点功能就是Magento的API。
    他的API到底适合做什么呢?
    
    我们罗列了目前我们已经实施的API业务:
    1 物流整合API,可以实现物流的自动收发通知
    2 ERP库存和订单整合
    3 客户关系管理,整合客户信息到外部邮件订阅系统以及客户关系管理系统
    4 支付接口对接,由于特殊的支付模式需要通过API端口后端支付
    5 多系统产品同步。
    
    以后的预期通过API我们还将会操作更多的功能和特色:
    1 开发方面将会通过API做到单元测试
    2 功能模块方面将会通过API进一步实现 外部系统 和 内部系统 的支付,配送,订单一体化。最终完善系统,实现信息整合。
    

  • Solve Magento Enterprise Edition's Private Sale Cookie Problem(Expire and Login Problem)

    7 year(s) ago

    We find out that Magento CE 1.3+ and Magento EE 1.7+ has the problem on the Safari and Google Chrome browser.
    
    These browser detect the client's timezone/machine time and calculate the cookie's expireation time.So if you have a customer on the specified environment. They can't login to the Magento system.
    
    This problem was found on the Magento EE 1.7+ seriously.(Private Sale mode)
    
    What we can fix  is:
    
    Solution1:Recalculate the cookie expireation on the Frontend(Via Javascript)
    
    Solution2:Use a very long expireation method to avoid the cookie problem
    
    Solution3:Coding in the Core/Cookie and try to make the expireatoin time depend on client timezone and not the server side.
    
    CosmoCommerce try to use the solution 3 and find out it may take the side effect to the system for some security reason. So we have to use solution 2 instead.
    
    If you have same problem ,welcome the feedback.
    

  • 关于开源云平台与电子商务

    7 year(s) ago

    目前的开源云平台有两个阵营:
    
    1 UEC/Eucalyptus
    Eucalyptus 在Ubuntu 企业版的UEC中 实现了 节点控制器和存储控制器以及Cluster控制器的核心构成。
    
    2 OpenStack
    最近由RackSpace国外著名的云平台商提供开源
    
    两者的区别目前来看,前者更为成熟稳定,支持较多,应用完善。在企业私有云份额已经很大。但是由于企业发展的长期性问题会涉及到的核心代码开放问题,这部分在企业成长到很大时候将会遇到,这一点制约了Eucalyptus在企业私有云内部的实现,从而导致了其他企业对Eucalyptus的支持不够,使得整个产品的整合交互能力不足。
    
    目前的OpenStack由于是新产品,故其发展速度很快。支持厂商众多。
    目前其分为 云计算 和 云存储 两个部分。
    
    详细介绍:http://www.openstack.org/
    
    未来电子商务在企业内部的实现由于会涉及到整合企业内部资源,保障企业运行环境的高效化。所以我们需要云平台来最大资源调度。
    
    场景如下:
    
    1 电子商务企业初期预计前端服务器和后端存储数据库的性能,由于数据不充分无法预估配置性能以及集群规模,因此需要在云平台上先期部署 前置端集群和后置端集群,通过采集初期数据采集进行动态调整资源。实现企业业务系统的资源最大化利用。也可以避免过高的采购费用影响企业初期项目实施。
    
    2 规模化企业由于内部支持系统的资源剩余,导致其有需求最大利用平台调度能力进行动态规划系统。
    
    3 企业内部系统的快速恢复与快照能力。
    

  • Magento and PHP's Cookie and Session

    7 year(s) ago

    PHP Part
    
    1 Set Cookie:
    header('set-cookie:user=cosmocommerce');
    setcookie('user', 'cosmocommerce');
    
    2 Delete Cookie:
    
    setcookie('user_name_1');                //Same lifetime with browser
    setcookie('user_name_2', "", time()-1); // Expired
    
    3 Session:
    
    bool   session_start(void);//init session
    bool   session_destroy(void)//delete session
    string session_id() //get session id
    string session_name() //get session name(default PHPSESSID)
    array session_get_cookie_params()
    string session_cache_limiter()
    ini    session_cache_expire()
    bool   session_destroy()
    void   session_set_cookie_params ( int lifetime [, string path [, string domain [, boolsecure [, bool httponly]]]] )
    bool session_set_save_handler ( callback open, callback close, callback read, callbackwrite, callback destroy, callback gc )
    bool session_regenerate_id([bool delete_old_session])
    
    Magento Part
    
    1  Model:
    
    Mage::getModel('core/cookie');
    
    Mage::getModel('core/session');
    
    2 Set Method:
    
    Mage::getSingleton('core/cookie')->set('name','value');
    Mage::getSingleton('core/session')->set('name','value');
    
    3 Get method:
    
    Mage::getSingleton('core/cookie')->get('name');
    Mage::getSingleton('core/session')->get('name');
    
    Other Method please check:
    
    app/code/core/Mage/Core/Model/Session.php
    
    app/code/core/Mage/Core/Model/Cookie.php
    

  • 搜索引擎营销

    7 year(s) ago

    搜索引擎营销是与搜索引擎优化相对应的概念。

    当客户进入网站以后,对客户行为与访问的确定并进行针对性的营销策略是SEM的关注重点。

    我们通过使用完全免费的Google Analystic或者当您购买了Sitecatalyst之后,我们将会提供SEM的咨询服务。

    对您的网站如何更加有效的吸引有效访客给与宏观的策略支持和微观的人机界面,页面流程等的咨询

Items 1 to 20 of 178 total

per page

Set Ascending Direction