Implement Google ReCaptcha Enterprise with score-based approach in Laravel

Magento Wordpress Related Post using fishpig integration display Related Post

1.1 Defining your module

Once you've set up Magento and entered it into the root Magento directory, go into app/code/local/. This will be where your module lives on the system. The first folder is your namespace, usually your company name. Then directory underneath this is your module name.

All your module folders will live underneath this module directory. We will create many here, but for starters just create the etc/ and controllers/ directories. We will also create a file called config.xml in this etc/ directory. This is the main, and incredibly important, the configuration file for your module.

Create this folder structure now. Your directory layout should look as follows:

[magentodir]/app/code/local/NAMESPACE/MODULENAME/etc/config.xml

[magentodir]/app/code/local/NAMESPACE/MODULENAME/controllers/

The content of config.xml should be as follows. It adds this module to the rest of the <modules> in the Magento system. And everything is in a module, even the 'core' Magento classes live within modules.

This config.xml specifies the full module name and a version number. The module name, NAMESPACE_MODULE, is derived from the aforementioned folder name. This is a very common pattern in Magento. Take note.

FILE: app/code/local/NAMESPACE/MODULENAME/etc/config.xml

<config>
<modules>
<NAMESPACE_MODULENAME>
<version>0.1.0</version>
</NAMESPACE_MODULENAME>
</modules>
</config>

 

But before the system can actually see your new module you need another config file. This is because the Magento system won't traverse every folder in app/code/local looking for a config.xml file. Instead, it looks in app/etc/modules/ and processes every XML file there. This XML file is similar to the last but without a version number. It specifies that the module is <active>. And that it lives in the local ‘codePool', which means it's in app/code/local. To create this file in app/etc/modules. Its name is the module name as above.

FILE: app/etc/modules/NAMESPACE_MODULENAME.xml

 

<config>
<modules>
<NAMESPACE_MODULENAME>
<active>true</active>
<codePool>local</codePool>
</NAMESPACE_MODULENAME>
</modules>
</config>

 

Now if we flush out the Magento cache in the admin panel (via System->Cache Management->Flush Magento Cache button), and go to System->Configuration->Advanced you should see your module in the list. 

 

 

 

1.2 Declaring your controller 'routes'

But our module doesn't actually do anything currently. We need to add a 'route' going from a URL to a class we define. This will in turn actually do something. Alter your config.xml like so to add that route.

This modification we're adding to the <frontend> of the system (i.e. not the admin panel). And we're adding a router to the other <routers> in the system. We're giving that router a name, useful when dealing with layouts later on.

Then we say it <use>s the ‘standard’ frontend router system. Then it defines the important arguments (<args>): It’ll go to the <module> we’ve just defined. And it's all-important URL, called the <frontName>.

 

FILE: app/code/local/NAMESPACE/MODULENAME/etc/config.xml

 

<config>
<modules>
<NAMESPACE_MODULENAME>
<version>0.1.0</version>
</NAMESPACE_MODULENAME>
</modules>
   <frontend>
<routers>
<ITSROUTERNAME>
<use>standard</use>
<args>
<module>NAMESPACE_MODULENAME</module>
<frontName>URLNAME</frontName>
</args>
</ITSROUTERNAME>
</routers>
</frontend>
</config>

 

 

1.3 Defining the controller class

We’ll now define the PHP class that will be called via that route. Meaning, it will be called when the user goes to <magentourl>/URLNAME.

This will call a class in your controllers/ module directory. The default class that it will call is IndexController.php. And within that class the default method it will call will be indexAction(). All controller class methods called from the outside must have 'Action' suffixed to their name.

If you don’t use these defaults, you have to specify the controller name and action name after URLNAME i.e. [magentourl]/URLNAME/controllername/actionname, as opposed to just [magentourl]/URLNAME. [magentourl]/URLNAME/index/index is the same as just loading [magentourl]/URLNAME

Let’s create that controllers/IndexController.php class now. Its name must be prepended by the Namespace and Module name. All controllers must must have the word Controller at the end. (But you don’t need to use the word 'Controller' should you need to specify the controller in the url.)

The will extend Mage_Core_Controller_Front_Action to allow it to work as a controller and to give it access to various methods and properties of the system.

FILE: app/code/local/NAMESPACE/MODULENAME/controllers/IndexController.php

 

<?php
class NAMESPACE_MODULENAME_IndexController 

               extends Mage_Core_Controller_Front_Action 

   {
public function indexAction() 

       {
echo 'hihi!';
}

   }

?>

So if you go to <magentourl>/URLNAME you should see your new page. It will do nothing except displaying the words 'hihi'. Not impressive--but a start. 

 

You may also want to define a route to the admin panel. But that topic will be dealt with after part I. This is because you will be applying much of what you have learnt dealing with Magento's front end.

In this post I will show how you can add banner ads to your Ionic apps. I will be doing this on a new app but you can do it to your existing app as well. I have also written a post on adding banner ads to Ionic 2 apps, so if you are looking for Ionic 2 apps You can check that post out as well.

Step 1)

We will first start by creating a new Ionic project by issuing the following command in the command prompt

Step 2)

Now we will need to add the platform to out app. So will do the following command

Step 3)

As we will be using the AdMob Pro plugin we will need to download it in our project. We will do that by the following command

you can read more about the plugin in the Admob pro plugin documentation

Step 4)

Now we will need to add the following code to the $ionicPlatform.ready() in the app.js file

So the finished app.js file looks like this:

NOTE: The app.js file will be different for each template namely tabs,bank,sideMenu, make sure you add the code to the $ionicPlatform.ready() function and no to any function inside it.

Introduction:
Few days ago I received a comment from one of the reader of my blog to show an example on CRUD (Create, Read, Update and Delete) with the database. So in this post we will explore the use of CRUD operation using SQLite database in PhoneGap application.

Description:
CRUD can be described as a process, which helps the user to add, view, search and modify the information inside the database.

Here are the basic steps which demonstrates CRUD operation.

• Create or add new entries
• Read, retrieve, search or view existing entries
• Update, modify or edit existing entries
• Delete, deactivate or destroy existing entries

Before doing any operation on database let’s initialize the database first, either using HTML5 local database concept or using SQLite plugin.

Let’s add the following javascript to initilze the database.

window.openDatabase helps to return the new database object. This method will create a the new SQLite database and also can be use for other data manipulation.

Above method will create the SQLite datebase with unlimited storage capacity. To integrate the SQLite plugin we can follow this post.

Now lets focus on the basic 4 steps of CRUD operation by using the database object already created by above step.

CREATE: Initializing or creating the table. We normally use two keywords CREATE and INSERT for this operation.

Example:

READ: Use to get, search or retrieve entries from a table inside the database.

Example:

UPDATE: This operation is used to update or modify the entries in the table.

Example:

DELETE: This is the last and final method of CRUD operation which is used to delete/drop the entries in table.

Example:

Summary:
I hope the above content will give some idea to start the basic CRUD operation with database and will make the life easy.

In Laravel 5 this has changed a bit. Now you can simply add the routes you want to exclude from CSRFToken verification, in $except an array of the class 'VerifyCsrfToken' (\app\Http\Middleware\VerifyCsrfToken.php):

class VerifyCsrfToken extends BaseVerifier 
{ 
protected $except = [ // Place your URIs here ]; 
}

Examples:

1. If you are using a route group:

Route::group(array('prefix' => 'api/v2'), function() { 
    Route::post('users/valid','UsersController@valid'); 
});

Your $except the array looks like:

protected $except = ['api/v2/users/valid'];

2. If you are using a simple route

Route::post('users/valid','UsersController@valid');

Your $except the array looks like:

protected $except = ['users/valid'];

3. If you want to exclude all routes under the main route (users in this case)

Your $except the array looks like:

protected $except = ['users/*'];

see: http://laravel.com/docs/master/routing#csrf-excluding-uris

Problem

if (!(bool)$debugMode && extension_loaded('xdebug')) { 
  xdebug_disable(); 
}

if (!(bool)$debugMode && extension_loaded('xdebug')) {
 if (function_exists('xdebug_disable')) {
 xdebug_disable();
 }
}

Magento AW Blog Integrated Search extends your default Magento search to include your Magento CMS pages and AW blog posts content in search results.  Blog contents are now listed in search results from integrated AW blog to ensure more keywords and content visibility to user. This extension will reduce the user bounce rate and keep your search more interactive and effective than before. You can add following results in default search in Magento

• Magento CSM pages
• AW Blog post
• Mage Search Tearm Improvement .

Integrating AW blog to Magento is a common way to have blog, more traffic and many more advantages. AW blog extension is well known for an effective blog in Magento community. Magento AW blog Integrated Search is compatible with AW blog extension.

How to Use this Extension

After install extension go to System -> Index Management .
In Index Management check “AW Blog Search Index” click “Reindex Data”

Customer can view the search result in front end using default magento search.

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”

AW Blog Report Generation extends used to generate user view AW Blog result count . Following
type of report you can see

• Report displayed by Days .
• Report displayed by Month .
• Report displayed by Year .

Features

• AW Blog User Visit Report .
• Used to Customer visting interest .
• Help to improve SEO of your Blog post .

Recomented

• Magento 1.7.x or Magento 1.8.x .
• AW Blog Magento Extension .

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':CordovaLib:processDebugResources'.
> com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command '/home/arulmanickam/adt-bundle-linux-x86-20131030/sdk/build-tools/23.0.2/aapt'' finished with non-zero exit value 127

Solution :

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