All posts by Pramod T P

Magento 2 Community Edition vs. Enterprise Edition

  • The Cost Difference
  • Customer Segmentation and Targeted Promotions to Drive Conversions
  • Customer Attribute Management for Advanced Personalization
  • Recommend, Up Sell and Cross Sell More Products with Rule Based Product Relations
  • Visual Merchandizer to Boost Conversions
  • Powerful Search to Drive Conversions
  • Limited Catalog Access to Display Products by Customer Group
  • Add to Cart by SKU to Improve Conversions
  • Streamline Returns with Advanced RMA
  • Drive Customer Loyalty and Rewards
  • Convert Returns into Future Sales with Store Credits
  • Keep Customers Coming back with Gift Cards
  • Promote Return Visits with Multiple Wish Lists
  • Increase Sales and Loyalty with a Custom Gift Registry
  • Private Sales and Personalized Shopping Experience
  • Increase Sales with Automated Email Reminders
  • Advanced Content Management Systems
  • Order Archiving to Make Store Management Convenient
  • Advanced Permissions for Improved Control
  • Support Tools to Quickly Diagnose and Resolve Issues
  • Content Staging and Preview
  • Architecture that Scales with your Business
  • MySQL Cluster Support for High Availability
  • Drive Performance with Message Queues
  • Support for Alternate Media Storage – CDN and Database
  • You are in Safe Hands with Strong Data Encryption, Hashing and Key Management
  • Dedicated Support for the Difficult Times

Deploy Static Content Magento 2

The static view files deployment command enables you to write static files to the Magento file system .

The term “Static” means it can be cached for a site( images ,JS and CSS )

The term “View” refers to the presentation layer (from MVC).

Static view files are located in the pub/static directory, and some are cached in the var/view_preprocessed directory as well.

Static view files deployment is affected by Magento modes as follows:

Default and developer modes: Magento generates them on demand, but the rest are cached in a file for speed of access.

Production mode: Static files are not generated or cached.

You can deploy the static content by running the below command.

php bin/magento setup:static-content:deploy


magento 2 technical problem with the server created an error

I have faced the same issue and its like the system was throwing the below error

Magento ver. 2.2.0-dev – A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later

To fix the issue I have deployed the static content again and done reindexing and cache clearing

php bin/magento setup:static-content:deploy

php bin/magento indexer:reindex

php bin/magento cache:flush


PHP FastCGI Process Manager

FPM (FastCGI Process Manager) is an alternative PHP FastCGI implementation with some additional features (mostly) useful for heavy-loaded sites.

These features include:

advanced process management with graceful stop/start;

ability to start workers with different uid/gid/chroot/environment, listening on different ports and using different php.ini (replaces safe_mode);

stdout and stderr logging;

emergency restart in case of accidental opcode cache destruction;

accelerated upload support;

“slowlog” – logging scripts (not just their names, but their PHP backtraces too, using ptrace and similar things to read remote process’ execute_data) that are executed unusually slow;

fastcgi_finish_request() – special function to finish request and flush all data while continuing to do something time-consuming (video converting, stats processing etc.);

dynamic/static child spawning;

basic SAPI status info (similar to Apache mod_status);

php.ini-based config file.