Search results for: 'how to cr2000eate custom workflow to send emails for event cr2000eation'

Magento Product email Notification to send mail to subscriber to new product created and every time
product save with the price changes . You can alert your subscriber about the your new product or
the product price change . It have the following option to send notification .

• Have an enable/disaple notification .
• Generate your own design email template .
• Email from name .
• Email from your email .

It have the feature to send newsletter of product notification manualy .

Feature

• Working with magento newsletter .
• Send mail to every subscriber.
• First time product save after "Mage Product Email Notification" extension installed .
• Every time product price changed increase or decrease .
• Mail sent only a product visibility "Enables" & Product have a stock .
• Manual send Newsletter of product notification .
• Related Product also added to email .
• Manual feach the subscriber log .
• Cron to Send mail .
• limit Daily mail .
• Limit to Daily mail per eamil .
• Limit to Mail Per cron .
• Send Mail by Email Order by Descending .
• Send Mail by Price Order by Descending .
• Send Mail by Product ID Order by Descending .

Newsletter Variable

Newsletter Variable can use in Transactional Emails

• {{var items_html}} get Product detail { Name , Description , Price } .
• {{var items_related}} get 3 Related Product detail { Name , Description , Price } .

With the support of seamless customization and integrations, Magento 2 e-commerce stores can serve excellent experiences to customers. In many cases, the store owners are willing to allow the shoppers to add the product to the cart with a custom price.

Frequently, the store owner is prepared to set a fixed product pricing even if the consumer selects various options/add-ons from the front end for all or some specific products. Instead of manually changing all store products, we’ll need to manually code to override all store product prices with your preferred custom price.

In this article, I will instruct you to set a custom price of the product when adding the product to the cart by using Observe.

Let’s explore two straightforward steps below!

Step 1: Create Events/xml File

Firstly, you need to create events/xml in the folder Mageplaza/HelloWord/etc/frontend and use event checkout_cart_product_add_after

<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:Event/etc/events.xsd">
    <event name="checkout_cart_product_add_after">
        <observer name="customprice" instance="Mageplaza\HelloWord\Observer\CustomPrice" />
    </event>
</config>
 

Step 2: Create CustomPrice.php File

Now, you have to create CustomPrice.php file that overrides your price in the Observer Folder.

<?php
    /**
     * Mageplaza Hello CustomPrice Observer
     *
     * @category    Mageplaza
     * @package    Mageplaza_HelloWord
     *
     */
    namespace Mageplaza\HelloWord\Observer;
 
    use Magento\Framework\Event\ObserverInterface;
    use Magento\Framework\App\RequestInterface;
 
    class CustomPrice implements ObserverInterface
    {
        public function execute(\Magento\Framework\Event\Observer $observer) {
            $item = $observer->getEvent()->getData('quote_item');         
            $item = ( $item->getParentItem() ? $item->getParentItem() : $item );
            $price = 100; //set your price here
            $item->setCustomPrice($price);
            $item->setOriginalCustomPrice($price);
            $item->getProduct()->setIsSuperMode(true);
        }
 
    }

Note: According to your need for setting a custom price for one or more products, you can manipulate this by adding conditions.

Conclusion

That is the detailed instruction on how to add the product to the cart with the custom price in Magento 2. Let us know if you have any questions by commenting below!

Magento e-commerce has a standard newsletter function that is useful if you get it to work. This post will highlight the major reasons why your newsletter is not sent to your customers.

1. Magento schedules and sends the newsletters using a cronjob script called “cron.php” in your Magento installation root folder. To schedule this cronjob you need to access your web server using SSH (You can use for example Putty). For more information see the Magento wiki.
2. If you don’t want to schedule the cronjob you need to go twice to the cron.php file in your browser e.g. www.yoursite.com/cron.php every time you want to send your newsletter. The first time it will schedule the newsletter and the second time it will send it.
3. After login with ssh type: crontab -e This will open an editor. The contents may be empty if you have never set up crontabs for the current user.
4. To schedule the cronjob every 5 minutes you should enter: */5 * * * * php /absolute/path/to/magento/cron.php
5. Save and close
6. Now you can create a newsletter template at Newsletter / Newsletter Templates.

   Create Newsletter

7. After creating and saving the template you can schedule it by selecting “Queue Newsletter” in the Action pull-down.

   Queue newsletter

8. Select a date and time at “Queue Date Start” when you want to start sending your newsletter.
9. If you have multiple store views make sure you select at least one store view at “Subscribers From” otherwise you will have no recipients.
10. Click on “Save Newsletter” and you will see the scheduled newsletter at the Newsletter Queue.

    Queue Newsletter

11. If everything goes right you will see that after a while all the recipients will receive the newsletter and the status should be “Sent”

Add wysiwyg editor in magento custom module. is very easy to make it in your magento custom modue use this following method to add wysiwyg editor .

go to the file

{your magento root folder}/Block/Adminhtml/{module name}/Edit/Tab/Form.php

add following code in top of the file

$fieldset->addField('followupemail_text', 'editor', array( 

'name'=>'followupemail_text',

'label' => Mage::helper('followupemail')->__('Content'),

'title' => Mage::helper('followupemail')->__('Content'),

'required' => true,

'style' => 'height:24em;',

'config' => $wysiwygConfig, ));

 

go to the file

{your magento root folder}/Block/Adminhtml/{module name}/Edit.php

add the following line in this file

protected function _prepareLayout()

{

// Load Wysiwyg on demand and Prepare layout

if (Mage::getSingleton('cms/wysiwyg_config')->isEnabled() && ($block = $this->getLayout()->getBlock('head')))

{

$block->setCanLoadTinyMce(true);

}

parent::_prepareLayout();

}

As you know, configuring robot.txt is important to any website that is working on a site’s SEO. Particularly, when you configure the sitemapto allow search engines to index your store, it is necessary to give web crawlers the instructions in the robot.txt file to avoid indexing the disallowed sites. The robot.txt file, that resides in the root of your Magento installation, is directive that search engines such as Google, Yahoo, Bing can recognize and track easily. In this post, I will introduce the guides to configure the robot.txt file so that it works well with your site.

Following steps to Configure robots.txt in Magento 2

• On the Admin panel, click Stores. In the Settings section, select Configuration.
• Select Design under General in the panel on the left
• Open the Search Engine Robots section, and continue with following:
  • In Default Robots, select one of the following:
    • INDEX, FOLLOW
    • NOINDEX, FOLLOW
    • INDEX, NOFOLLOW
    • NOINDEX, NOFOLLOW
  • In the Edit Custom instruction of robots.txt File field, enter custom instructions if needed.
  • In the Reset to Defaults field, click on Reset to Default button if you need to restore the default instructions.
• When complete, click Save Config.

Examples of Custom Robots.txt file

• Allows Full Access

User-agent:* 
Disallow: 

• Disallows Access to All Folders

User-agent:* 
Disallow: / 

Default Robots.txt for Magento 2

Disallow: /lib/ 
Disallow: /*.php$ 
Disallow: /pkginfo/ 
Disallow: /report/ 
Disallow: /var/ 
Disallow: /catalog/ 
Disallow: /customer/ 
Disallow: /sendfriend/ 
Disallow: /review/ 
Disallow: /*SID= 
Disallow: /*? # Disable checkout & customer account 
Disallow: /checkout/ 
Disallow: /onestepcheckout/ 
Disallow: /customer/ 
Disallow: /customer/account/ 
Disallow: /customer/account/login/ # Disable Search pages 
Disallow: /catalogsearch/ 
Disallow: /catalog/product_compare/ 
Disallow: /catalog/category/view/ 
Disallow: /catalog/product/view/ # Disable common folders 
Disallow: /app/ 
Disallow: /bin/ 
Disallow: /dev/ 
Disallow: /lib/ 
Disallow: /phpserver/ 
Disallow: /pub/ # Disable Tag & Review (Avoid duplicate content) 
Disallow: /tag/ 
Disallow: /review/ # Common files 
Disallow: /composer.json 
Disallow: /composer.lock 
Disallow: /CONTRIBUTING.md 
Disallow: /CONTRIBUTOR_LICENSE_AGREEMENT.html 
Disallow: /COPYING.txt 
Disallow: /Gruntfile.js 
Disallow: /LICENSE.txt 
Disallow: /LICENSE_AFL.txt 
Disallow: /nginx.conf.sample 
Disallow: /package.json 
Disallow: /php.ini.sample 
Disallow: /RELEASE_NOTES.txt # Disable sorting (Avoid duplicate content) 
Disallow: /*?*product_list_mode= 
Disallow: /*?*product_list_order= 
Disallow: /*?*product_list_limit= 
Disallow: /*?*product_list_dir= # Disable version control folders and others 
Disallow: /*.git 
Disallow: /*.CVS 
Disallow: /*.Zip$ 
Disallow: /*.Svn$ 
Disallow: /*.Idea$ 
Disallow: /*.Sql$ 
Disallow: /*.Tgz$ 

More Robots.txt examples

Block Google bot from a folder

User-agent: Googlebot 
Disallow: /subfolder/ 

Block Google bot from a page

User-agent: Googlebot 
Disallow: /subfolder/page-url.html 

Common Web crawlers (Bots)

Here are some common bots in the internet.

User-agent: Googlebot 
User-agent: Googlebot-Image/1.0 
User-agent: Googlebot-Video/1.0 
User-agent: Bingbot 
User-agent: Slurp # Yahoo 
User-agent: DuckDuckBot 
User-agent: Baiduspider 
User-agent: YandexBot 
User-agent: facebot # Facebook 
User-agent: ia_archiver # Alexa

Here we learn how to write custom mysql query in Magento2.

Suppose we have table ’employee’ with fields emp_id, emp_name, emp_code and emp_salary.

Custom Mysql Query

            $objectManager = \Magento\Framework\App\ObjectManager::getInstance(); // Instance of object manager
            $resource = $objectManager->get('Magento\Framework\App\ResourceConnection');
            $connection = $resource->getConnection();
            $tableName = $resource->getTableName('employee'); //gives table name with prefix

            //Select Data from table
            $sql = "Select * FROM " . $tableName;
            $result = $connection->fetchAll($sql); // gives associated array, table fields as key in array.

            //Delete Data from table
            $sql = "Delete FROM " . $tableName." Where emp_id = 10";
            $connection->query($sql);

            //Insert Data into table
            $sql = "Insert Into " . $tableName . " (emp_id, emp_name, emp_code, emp_salary) Values ('','XYZ','ABD20','50000')";
            $connection->query($sql);

            //Update Data into table
            $sql = "Update " . $tableName . " Set emp_salary = 20000 where emp_id = 12";
            $connection->query($sql);

So, you must follow the instructions for sites that use custom page templates. The process I've followed

• log into BigCommerce and create a new page. In this case, the page is "/newsletter/"
• Edit config.stencil.json and add it to the customLayouts -> page list (see below)
• Create and edit [sitehome]/templates/pages/custom/page/newsletter.html
• View the page locally and verify that it appears as expected.
• Perform a stencil push.

{
  "customLayouts": {
    "brand": {},
    "category": {},
    "page": {
      "locations.html":"/our-stores/",
      "employment.html":"/employment/",
      "newsletter.html":"/newsletter/",
      "ask-beth.html":"/ask-beth/"
    },
    "product": {}
  },
  "apiHost": "https://api.bigcommerce.com",
  "normalStoreUrl": "https://www.samdoit.com",
  "port": 3000
}

So, you must follow the instructions for sites that use custom page templates. The process I've followed

• log into BigCommerce and create a new page. In this case, the page is "/newsletter/"
• Create .stencil and add it to the customLayouts -> page list (see below)
• Create and edit [sitehome]/templates/pages/custom/page/newsletter.html
• View the page locally and verify that it appears as expected.
• Perform a stencil push.

{
  "customLayouts": {
    "brand": {},
    "category": {},
    "page": {
      "locations.html":"/our-stores/",
      "employment.html":"/employment/",
      "newsletter.html":"/newsletter/",
      "ask-beth.html":"/ask-beth/"
    },
    "product": {}
  },
  "apiHost": "https://api.bigcommerce.com",
  "normalStoreUrl": "https://www.samdoit.com",
  "port": 3000,
  "clientId": "xxxxxxxxxxxxxxxxx",
  "accessToken": "xxxxxxxxxxxxxxxxxx"
}

You have created a new entity type and want to display it as a paginated list ?

First, integrate the MagePageBlockHtmlPager through your block :

class Your_Module_Block_Entityname_ListextendsMage_Core_Block_Template {

 protectedfunction _construct() {

  parent::_construct(); 

// We get our collection through our model  

$this->_entities = Mage::getModel('your_module/entityname')
->getCollection() 
->setOrder('created_at'); 

// Instantiate a new Pager block  

$pager =newMage_Page_Block_Html_Pager(); 

// We set our limit (here an integer store in configuration).  

// /!\ The limit must be set before the collection  

$pager->setLimit((int)Mage::getStoreConfig('your_module/entityname/pagination')) 
->setCollection($this->_entities); 

// Add our Pager block to our current list block  

$this->setChild('pager', $pager); 

} 

} 

ou just need now to include the call in your template (phtml) file :

 <divclass="your_module_entities"> 

 <?php foreach($this->_entities as $entity):?>

  <divclass="entity">

  <h2><?php echo $entity->getAttribute1();?></h2>

  <p><?php echo $entity->getAttribute2();?></p>

  </div> 

 <?php endforeach;?>

  </div> 
<?php echo $this->getChildHtml('pager');?>

And you should be good to go !

Third Party Platform interact with Magento 2 by API. When you are working for API related stuff and using SearchCriteriaBuilder Object for your query and if you want to apply OR conditions for custom query, You need to define setFilterGroups([Object]) for OR query.

Whenever you are dealing with SearchCriteriaBuilder in Magento 2, You might be need to query with OR conditions for custom requirement, You can give OR conditions to Magento\Framework\Api\SearchCriteriaBuilder by simple code snippets.

Let’s imagine, We built a query using OR conditions for Products.

Fetch collection of only those products whose sku is like `MSH01%` OR `type_id` is equal to simple.

<?php
namespace Rbj\Training\Block;

class Training extends \Magento\Framework\View\Element\Template
{
    public function __construct(
        \Magento\Framework\View\Element\Template\Context $context,
        \Magento\Catalog\Api\ProductRepositoryInterface $productRepository,
        \Magento\Framework\Api\SearchCriteriaBuilder $searchCriteriaBuilder,
        \Magento\Framework\Api\FilterBuilder $filterBuilder,
        \Magento\Framework\Api\Search\FilterGroupBuilder $filterGroupBuilder,
        array $data = []
    ) {
        $this->customerRepository = $customerRepository;
        $this->searchCriteriaBuilder = $searchCriteriaBuilder;
        $this->filterBuilder = $filterBuilder;
        $this->filterGroupBuilder = $filterGroupBuilder;
        parent::__construct($context, $data);
    }

    /**
     * OR condition for searchCriteriaBuilder
     */
    public function applyOrCondition() {
        $filter_1 = $this->filterBuilder
            ->setField('sku')
            ->setConditionType('like')
            ->setValue('MSH01%')
            ->create();

        $filter_2 = $this->filterBuilder
            ->setField('type_id')
            ->setConditionType('eq')
            ->setValue('simple')
            ->create();

        $filter_group = $this->filterGroupBuilder
            ->addFilter($filter_1)
            ->addFilter($filter_2)
            ->create();

        // add filter group to setFilterGroups()
        $searchCriteria = $this->searchCriteriaBuilder
            ->setFilterGroups([$filter_group])
            ->create();

        $products = $this->productRepository->getList($searchCriteria)->getItems();
        return $products;
    }

Using Magento\Framework\Api\FilterBuilder class, You need to create filterBuilder for your separate field.

using Magento\Framework\Api\Search\FilterGroupBuilder class, apply AND conditions to addFilter( ) with filterGroupBuilderobject.

Now Our searchCriteriaBuilder instance is ready for fetch collection of products,
$products = $this->productRepository->getList($searchCriteria)->getItems();
gives the result of our OR query for a products.

This article shows how we can search Magento Repositories using SearchCriteriaBuilder that implements SearchCriteriaInterface. An example is provided of how we can perform search on Product repository in Magento. Similarly, we can search for other entities like Category, Customer, Order, Invoice, CMS Page, CMS Block, etc.

We can add different conditions to build custom search criteria.

Filters

Filter class is used to add custom field, value, and condition type to the search criteria.

$filter
    ->setField("name")
    ->setValue("%laptop%")
    ->setConditionType("like");

• condition_type is optional.
• If condition_type is not provided then the default condition_type is set as eq.

Different condition types:

CONDITION   NOTES
eq          Equals
gt          Greater than
gteq        Greater than or equal
lt          Less than
lteq        Less than or equal
moreq       More or equal
neq         Not equal
in          The value can contain a comma-separated list of values.
nin         Not in. The value can contain a comma-separated list of values.
like        The value can contain the SQL wildcard characters when like is specified.
nlike       Not like
notnull     Not null
null        Null
finset      A value within a set of values
nfinset     A value that is not within a set of values.
from        The beginning of a range. Must be used with to.
to          The end of a range. Must be used with from.

Filter Groups

FilterGroup class is used to apply multiple search criteria filters.

For OR condition: Pass filters array inside the FilterGroup class object.
For AND condition: Pass filterGroups array inside the searchCriteria class object.

$filter1
    ->setField("name")
    ->setValue("%laptop%")
    ->setConditionType("like");

$filter2
    ->setField("store_id")
    ->setValue("1")
    ->setConditionType("eq");

$filterGroup1->setFilters([$filter1, $filter2]);

$filter3
    ->setField("url_type")
    ->setValue(1)
    ->setConditionType("eq");

$filterGroup2->setFilters([$filter3]);

$searchCriteria->setFilterGroups([$filterGroup1, $filterGroup2]);

The above code will generate the following conditions:

(name like %laptop% OR store_id eq 1) AND (url_type eq 1)

Sorting

SortOrder is used to apply sorting to the search criteria.

Field and Direction can be passed to the sortOrder object.

Field is the name of the field to sort.
Direction is how we would like to sort the result. The two sorting values are ASC and DESC.

$sortOrder
    ->setField("email")
    ->setDirection("ASC");

$searchCriteria->setSortOrders([$sortOrder]);

Pagination

Limit the number in the result.

$searchCriteria->setPageSize(20); //retrieve 20 or less entities

Set the current page

$searchCriteria
    ->setPageSize(20)
    ->setCurrentPage(2); //show the 21st to 40th entity

The search engine determines the maximum number of results that a query can return.
For Elasticsearch, the default value of 10000 is defined in the module’s etc/di.xml file.

Search Items Using Filters

Below is an example of how we can search Product Repository using Search Criteria Builder.

The ProductRepositoryInterface class has the getList(SearchCriteria $searchCriteria) function which returns the search result object. The object is an instance of the class that implements the interface SearchResultInterface.

FilterBuilder and SearchCriteriaBuilder are used to avoid shared instances, i.e. we will be using create() method in the builder object so that Magento will instantiate a new object (unshared object).

use Magento\Framework\Api\SearchCriteriaBuilder;
use Magento\Framework\Api\FilterBuilder;
use Magento\Catalog\Api\ProductRepositoryInterface;
use Magento\Catalog\Api\Data\ProductInterface;
...
...
$filter = $this->filterBuilder
    ->setField(ProductInterface::NAME)
    ->setValue('%headphone%')
    ->setConditionType('like')
    ->create();

$this->searchCriteriaBuilder->addFilters([$filter]);
$this->searchCriteriaBuilder->setPageSize(20);

$searchCriteria = $this->searchCriteriaBuilder->create();
$productsItems  = $this->productRepository
    ->getList($searchCriteria)
    ->getItems();

Search Items using FilterGroups

Using FilterGroups to add multiple AND and OR conditions to search products.

use Magento\Framework\Api\SearchCriteriaBuilder;
use Magento\Framework\Api\FilterBuilder;
use Magento\Framework\Api\Search\FilterGroupBuilder;
use Magento\Catalog\Api\ProductRepositoryInterface;
use Magento\Catalog\Api\Data\ProductInterface;
...
...
$filter1 = $this->filterBuilder
    ->setField(ProductInterface::NAME)
    ->setValue("%laptop%")
    ->setConditionType("like")
    ->create();

$filter2 = $this->filterBuilder
    ->setField("store_id")
    ->setValue("1")
    ->setConditionType("eq")
    ->create();

$filterGroup1 = $this->filterGroupBuilder
    ->setFilters([$filter1, $filter2]);

$filter3 = $this->filterBuilder
    ->setField("url_type")
    ->setValue(1)
    ->setConditionType("eq")
    ->create();

$filterGroup2 = $this->filterGroupBuilder
    ->setFilters([$filter3]);

$this->searchCriteriaBuilder
    ->setFilterGroups([$filterGroup1, $filterGroup2]);

$this->searchCriteriaBuilder->setPageSize(20);

$searchCriteria = $this->searchCriteriaBuilder->create();
$productsItems  = $this->productRepository
    ->getList($searchCriteria)
    ->getItems();

Product Repository

use Magento\Catalog\Api\ProductRepositoryInterface;
use Magento\Catalog\Api\Data\ProductInterface;

Category Repository

use Magento\Catalog\Api\CategoryRepositoryInterface;
use Magento\Catalog\Api\Data\CategoryInterface;

CMS Page Repository

use Magento\Cms\Api\PageRepositoryInterface;
use Magento\Cms\Api\Data\PageInterface;

CMS Block Repository

use Magento\Cms\Api\BlockRepositoryInterface;
use Magento\Cms\Api\Data\BlockInterface;

Customer Repository

use Magento\Customer\Api\CustomerRepositoryInterface;
use Magento\Customer\Api\Data\CustomerInterface;

Order Repository

use Magento\Sales\Api\OrderRepositoryInterface;
use Magento\Sales\Api\Data\OrderInterface;

We had a requirement to check if one of our modules is enabled or not as two of our modules were sharing the same attribute code. We wanted to make sure that we don’t try to create an attribute again if the other module already installed or enabled.

We have done this many times in Magento 1 by using the following code snippet -:

Mage::helper('core')->isModuleEnabled('vendor_modulename');

So we were wondering there must be a simple way of doing this in Magento 2 as well and yes we were not wrong. It is not a single line of code as we had in Magento 1 but there is nothing in Magento 2 which can be implemented in Magneto 2 ???? You have to add dependency to get access to the functions.

Anyways let’s crack on with the code to find out if the module exists or enabled in Magento 2

<?php

class Custom
{
    /**
     * @var \Magento\Framework\Module\Manager
     */
    protected $_moduleManager;

    /**
     * @param \Magento\Framework\Module\Manager $moduleManager
     */
    public function __construct(
        \Magento\Framework\Module\Manager $moduleManager
    ) {
        $this->_moduleManager = $moduleManager;
    }


    /**
     * Returns if module exists or not
     *
     * @return bool
     * @throws \Magento\Framework\Exception\LocalizedException
     */
    public function isModuleEnabled()
    {
      return $this->_moduleManager->isEnabled('Scommerce_CatalogUrl');
    }
}

That’s it, Hope this article helped you in some way. Please leave us your comment and let us know what do you think? Thanks.