You might have received friend requests from many people but from few you would have not accepted or rejected because you were not sure and kept them waiting in your friend request list. Ever wondered the same could have happened for your requests to others. In this post we are going to learn how you can find out those people who didn’t accept/reject your friend requests and also learn how to cancel those pending friend requests. Don’t worry, your friend wouldn’t know that you have canceled the request.

How to find Pending Facebook Friend Requests

Log onto Facebook on your desktop browser and click on the friend requests icon on top right corner. It would open up a menu to show the list of friend requests that you have received. On the bottom of the screen there would be an option “See All”, which when clicked would show you an option to view the requests that you have sent.

You should be looking at something like below. If you still couldn’t follow, please click on this link.

How to cancel/undo a friend request

Now, if you have changed your mind and would like to cancel the Friend request that you have sent to any of these, you can hover on the “Friend Request Sent” and it would show an option to cancel the request.

Alternatively, if you know the person who you sent the request you can visit their profile page and when you hover on the “Friend Request Sent” option, you should be able to cancel the same request.

The post How to undo/cancel a Friend Request on Facebook appeared first on Technophileshub.

Either way, in this post we are going to address this problem through a Windows only technique called Junction, a variant of symbolic link. In case if you are wondering what a Symbolic Link is (a.k.a symlink), it is a shortcut that point to the original data that is stored in filesystem. There are different types of symlinks and Junction is a combination of soft and hard link. Let’s not get into details of these types for the sake of simplicity but just know that Junction is a shortcut that points to original file/directory.

Sync Folders to OneDrive (or) Dropbox (or) Google Drive

All the cloud service providers have their own software program that creates a sync folder on your PC. In most probabilities considering you have not changed the sync folder location they are available under your user folder in C drive. Look at the screenshots for each of these cloud services and their sync folder location.

1) Dropbox – Download and install Dropbox for Windows

2) Google Drive – Download and install Backup and Sync

3) OneDrive – Download and install OneDrive

Assuming that you know the location of the folder from which your cloud service syncs your files, next step is to sync the custom folder you want to be automatically synced.

As an illustration, let us sync one of our custom folders to Google Drive. Back up and Sync is linked to the folder “C:\Users\pavan\Google Drive”, so I would have to create a Junction in this folder pointing to the new custom folder that I wanted to be automatically synced.

The way we can create a Symbolic Link in windows is using command line command “MKLNK”. We have to use it with “/J” option to create a Junction link. For example

mklink /J "C:\Users\pavan\Google Drive\Documents" "E:\Pavans\Documents"

The first parameter for above command is the directory location where the Junction has to be created and the second location is the location where the Junction should point to.

With the above command we will now be able to sync all the files in Document folder of E drive to Google Drive without consuming the storage in C drive. You can try the same for different sync folder and should be able to get the same result.

Note: Please remember that your filesystem will not wipe off the memory allocated to the Junction folder as long as all the Junctions pointing to the directory are removed.

Hope you enjoyed the article and for any queries please comment below.

The post Automatically sync your custom folders to Google Drive or One Drive appeared first on Technophileshub.

In this post we are going to learn how we can create a simple conversational speech/chat bot that uses artificial intelligence to aid the IT Support Services. This post just serves as a proof of concept but not a complete solution.

Knowledge Requirements

Developing this bot requires you to have knowledge on Node and AI platforms.

Approach / Design

We are going to use DialogFlow AI (Formerly API.AI) to develop an intelligent Bot that can convert user concerns into an incident in Service Now, a major ticketing tool by market share (approx 52% as of today). The approach is to develop a NodeJS Server, which will act as back end and receive user inputs and queries AI. AI here acts as NLP by processing user input and gets required information from the conversation. We use the extracted information from AI in Node and consume services of ticketing tool to perform actions.

Action could be anything that you wish to perform and some of them could be

1. Creating a new Incident
2. Getting the current status of an existing Incident
3. Updating ticket with current status

Build / Deployment

As you can already see from Flow diagram we have to set up AI, NodeJS Application, Sandbox for Service Now and User Interface to complete the process. Let us go through each of them

AI Platform

We have to set up AI Platform first and it requires you to learn a little about how AI works. There are four key terms that you need to know and they are

1. Intent – To understand what user is trying to say from the conversation
2. Entity – To capture relevant parameters from the conversation
3. Action – Perform action based on the intent
4. Contexts – Understanding the situation of the conversation

Please go through documentation of any AI Platform to understand these terms better and for the sake of post, we are not going to go through them in detail.

Log into Dialgoflow with your email account and create an Agent.  This Agent responds to our application requests.

But as of now there is nothing to respond to our application. So, Google provided a simple plugin called Small Talk. By enabling this plugin, we can right away start a basic conversation and Agent can respond to that conversation. Enable this from your side navigation bar and save the Agent.

For now, we are done with basic conversation set up and I will share complete design of AI Project in download section.

NodeJS Application

We are going to use NodeJS as a hop between user and AI to have better control over the flow and bring in any programmatic changes during the process.

We have choice to use different packages in our Node application based on our requirement and design approach that we want to follow.

1. 1. 1. Express / Microsoft Bot Framework

      We need a UI Interface and we have multiple choices for this interface. We could have an experimental WebSpeech Interface to convert Speech to text and sent it to AI (or) We could use Skype chat interface. This leaves us to decide between Express and Microsoft Bot Framework and for the example, I am going to use Express.

      2. Socket.IO

      Socket.io enables real time bi-directional communication between user and NodeJS server through events and other option would be is to use asynchronous Ajax calls from the web application and provide the response in real-time back to the web application which in my opinion is not so effective.

      3. NLP/AI

      Not but not the least, we would need an NLP package to process the information that we have received from the user. Since we are talking about Google’s DialogFlow, the package required is apiai (Dialogflow is formerly api.ai). This package would need developer key and random access token for an instance and all it would take is a textRequest call to access our DialogFlow platform which we created above.

      Note: Please ensure that your design is compatible for future enhancements such as Google Actions. In case if you are writing application logic, please do it so as a programmable functions so that it can integrate well with google actions in future.

Now that application is ready, all it takes is to write application logic to read the response from AI or alternatively configure webhooks in AI and call the desired functions. For example, if the intent of the user was to create a ticket, call the function that provides the details to create ticket api of incident management tool.

In case if you are still wondering, I have github project for your reference to get you started or please feel free to leave comments below for any queries that you may have.

The post Creating a simple conversational speech bot using Dialogflow appeared first on Technophileshub.

1. Manage Files
2. Manage Databases

It would be a lengthy post to explain about both files and database in a single post, so we will discuss about managing files in this post and in other post we will discuss about managing databases

As the post name suggests, we are going to use Git to manage files in our remote website. Previously we used to use FTP to transfer files between web server and our local server. There are times when we missed to update a file on web server from local repository because we were not able to track the changes we have made to the files in our project. With Git, we can easily track changes in our local repository and web repository and ensure that we do not have any version discrepancies between repositories. This post assumes that you have SSH access to your web server, in case if you do not have access you may look for other alternatives such as Git-FTP for managing website but this post needs you to have SSH access.

In our first step, let us create a repository in our local system and this repository is root of our wordpress installation. Since we do not want every file to be managed by git. ( For example, the remote WordPress configuration is different from our local wordpress configuration, hence we do not want to manage “wp-config.php” file ). Let us create a “.gitignore” file and maintain list of files that should not be tracked by Git. I am using following gitignore file but you are free to create your own gitignore file based on your requirement.

# -----------------------------------------------------------------
# .gitignore for WordPress
# Bare Minimum Git
# http://ironco.de/bare-minimum-git/

# ver 20150227
#
# This file is tailored for a WordPress project 
# using the default directory structure
#
# This file specifies intentionally untracked files to ignore
# http://git-scm.com/docs/gitignore
#
# NOTES:
# The purpose of gitignore files is to ensure that certain files not
# tracked by Git remain untracked.
#
# To ignore uncommitted changes in a file that is already tracked,
# use `git update-index --assume-unchanged`.
#
# To stop tracking a file that is currently tracked,
# use `git rm --cached`
#
# Change Log:
# 20150227 Ignore hello.php plugin. props @damienfa
# 20150227 Change theme ignore to wildcard twenty*. props @Z33
# 20140606 Add .editorconfig as a tracked file
# 20140404 Ignore database, compiled, and packaged files
# 20140404 Header Information Updated
# 20140402 Initially Published
#
# -----------------------------------------------------------------

# ignore everything in the root except the "wp-content" directory.
/*
!wp-content/

# ignore all files starting with .
.*

# track this file .gitignore (i.e. do NOT ignore it)
!.gitignore

# track .editorconfig file (i.e. do NOT ignore it)
!.editorconfig

# track readme.md in the root (i.e. do NOT ignore it)
!readme.md

# ignore all files that start with ~
~*

# ignore OS generated files
ehthumbs.db
Thumbs.db

# ignore Editor files
*.sublime-project
*.sublime-workspace
*.komodoproject

# ignore log files and databases
*.log
*.sql
*.sqlite

# ignore compiled files
*.com
*.class
*.dll
*.exe
*.o
*.so

# ignore packaged files
*.7z
*.dmg
*.gz
*.iso
*.jar
*.rar
*.tar
*.zip

# ignore everything in the "wp-content" directory, except:
# "mu-plugins" directory
# "plugins" directory
# "themes" directory
wp-content/*
!wp-content/mu-plugins/
!wp-content/plugins/
!wp-content/themes/
!wp-content/uploads/

# ignore these plugins
wp-content/plugins/hello.php

# ignore specific themes
wp-content/themes/twenty*/

# ignore node/grunt dependency directories
node_modules/

With “.gitignore” in place, let us now create a local git repository.

$ cd <local_repo_dir>
$ git init
$ git add -A
$ git commit -m "Initial Version"

( <local_repo_dir> will be your wordpress installation directory )

We now have a local repository, let us create a remote repository as well, which will accept the changes from our local repository. Login to your ssh account.

ssh -p 2222 username@ipaddres

Once you logged in, verify if your server has git installed on it, this can be done by executing the command “git”. If command gives you an error, then your server do not have git installed. If you have authorizations, you can install git else you can raise a support ticket with webmaster.

Create a folder for remote repository, preferably above public web folder so that remote repository cannot be accessed from web. Since the remote repository on our server should accept push’s and pull’s from local repositories we need to make it a bare repository.

$ mkdir website.git && cd website.git
$ git init --bare

Now our remote repository is ready to receive the files from our local repository. At this point of time when you push the changes from your local repository to your server, changes would be in remote repository but they will not be reflected on your website because we did not move the files from our remote repository to the document root. If you want to move the files from this repository to document root as soon as you push from your local repository you can utilize the post-receive hook. Following post-receive script is a simple example for moving the changes to actual web repository

$ cat > hooks/post-receive
#!/bin/sh
GIT_WORK_TREE=<document_root> git checkout -f
$ chmod +x hooks/post-receive

Note:

• A bare git repository keeps files in compressed format so that it can transfer files between local repositories. By providing details of document root to GIT_WORK_TREE and checkout, we are telling git to keep files in working directory.
• We are using force checkout which will ignore remote repository HEAD detached state.
• Allowing the post-receive hook to have execution privilege is an important step for git to be able to move files to document root.

Let us now go back to our local repository and configure remote repository details so that we can push changes from local to remote repository. Following are the commands that you should execute

$ git remote add production ssh://yourdomain.com:<port>/<website.git>
$ git push production master

As soon as you execute these commands you must see that document root contains the files from our local repository. At this point of time we have only deployed our website from our local repository to remote repository and moving files from remote repository to document root. We are not tracking any changes to our document root folder and any changes to document root will not be present in our local repository. If you want to track the changes that you have made to the document root, it has to be a git repository as well.

Before we make our document root a git repository, let us add gitignore file from our local repository. Execute following command from your local repo.

scp -P2222 .gitignore username@domain.com:<document_root>

Now let us make our document root a git repository.

git clone ~/<yourwebsite.git> temp
mv temp/.git <document_root>/.git
rm -rf temp

Now we are ready to track changes to our document root using git. It would be a good idea to compare the differences between document root and remote repository before we push any changes from local repository. Alternatively, we can provide temporary path instead of document root and move files between temporary folder and document root but it would be little tedious task.

Making document root a git repository will allow us to push and pull from our remote repo.

git push production master

We can also use our remote repo to push or pull changes from our local repository.

git pull production master

One more thing that I would like to do before I wrap up this post is to edit your “.htaccess” file. Please add following line to your .htaccess file at top level root directory.

RedirectMatch 404 /\.git

In our next post, we will discuss how we can manage our database. Please feel free to provide feedback/comments/suggestions if you have any better way to manage.

The post How to manage remote wordpress website using Git appeared first on Technophileshub.

There are many different ways to embed Google driving directions, Following are some options

1. Fixed Destination
2. Fixed Destination address and User provided source address
3. Fixed Destination address and Dynamic Source Address Determination
4. User provided Destination Address and User provided Source Address
5. User provided Destination Address and Dynamic Source Address Determination

I cannot think of any other ways but there could be some other way that you might have in your mind. All these ways can be implemented in many different ways as pointed out earlier. Let us take a look at the options that we have

1) Embed Code from Google Maps

Google directly provides you with the embed code once you have loaded the map in Google Maps. But the disadvantage with this method is that you do not have neither the dynamic source or dynamic destination. If you do not need these dynamic determination of addresses, this is the way for you. All you have to do is load up the map in http://www.google.com/maps and provide the source and destination. This will load the map that you want and once it is loaded click on that little gear icon below to open up the settings menu. Here you find the “Share or embed map” option. In case if that button below is not available, you will find expand icon just above the source address which when clicked opens up the side panel where you have the same embed option.

Map below is embedded using this technique.

2) Google Map API

Google has the Embed API just for this, you can read more about this API @ https://developers.google.com/maps/documentation/embed/ . Although this is a simple API to use, you need to register your application to get the API key. Following is the syntax that you have to use to embed a map.

<iframe width="600" height="450" frameborder="0" style="border:0"
src="https://www.google.com/maps/embed/v1/directions?origin=...&destination=...&key="></iframe>

By looking at the pattern above we can notice that it is form data with origin, destination and key parameters. Hence we can develop our own form and submit the result to an iFrame to get the directions. I have written a sample HTML page to do this you can clone it from Google Map Directions GitHub.

<!doctype html>
<html lang="en">
   <head>
        <title>jQuery mobile with Google maps</title>
        <script src="https://maps.googleapis.com/maps/api/js?v=3.exp&signed_in=true&libraries=places"></script>
        <script type="text/javascript">
        function setiFrameSource(){
            var iFrame = document.getElementById("iFrame");
            var Url = "https://www.google.com/maps/embed/v1/directions?";
            var origin = "origin=".concat(document.getElementById("origin").value).concat("&");
            var destination = "destination=".concat(document.getElementById("destination").value).concat("&");
            var key = "key=".concat(document.getElementById("key").value);
            Url = Url.concat( origin, destination, key );
            iFrame.src= Url;
        }
        function initialize() {
          // Create the autocomplete object, restricting the search
          // to geographical location types.
          origin = new google.maps.places.Autocomplete(
              /** @type {HTMLInputElement} */(document.getElementById('origin')),
              { types: ['geocode'] });
          destination = new google.maps.places.Autocomplete(
              /** @type {HTMLInputElement} */(document.getElementById('destination')),
              { types: ['geocode'] });
          // When the user selects an address from the dropdown,
          // populate the address fields in the form.
          google.maps.event.addListener(origin, 'place_changed', function() {
            fillInAddress();
          });
          google.maps.event.addListener(destination, 'place_changed', function() {
            fillInAddress();
          });
        }
        // [START region_geolocation]
        // Bias the autocomplete object to the user's geographical location,
        // as supplied by the browser's 'navigator.geolocation' object.
        function geolocate() {
          if (navigator.geolocation) {
            navigator.geolocation.getCurrentPosition(function(position) {
              var geolocation = new google.maps.LatLng(
                  position.coords.latitude, position.coords.longitude);
              var circle = new google.maps.Circle({
                center: geolocation,
                radius: position.coords.accuracy
              });
              autocomplete.setBounds(circle.getBounds());
            });
          }
        }
</script>
    </head>
    <body onload="initialize()">
        <form method="get" target="iFrame">
        <input id="origin" style="width:82%;" placeholder="Put Origin here" name="origin" type="text" onFocus="geolocate()"/>
        <input id="destination" style="width:82%;" placeholder="Put Origin here" name="destination" type="text" onFocus="geolocate()"/>
        <input id="key" type="hidden" name="key" value="AIzaSyD4iE2xVSpkLLOXoyqT-RuPwURN3ddScAI">
        <input style="width:8%;" type="button" value="Go" onclick="setiFrameSource();"/>
        </form>
        <iframe id="iFrame" name="iFrame" src="https://www.google.com/maps/embed/v1/directions?origin=Hyderabad&destination=JNTU Busstop&key=AIzaSyD4iE2xVSpkLLOXoyqT-RuPwURN3ddScAI" style="height:500px;width:500px" ></iframe>


    </body>
</html>

This is just an example of what  you can do with Google Maps API, you can refer to the documentation to know more about it. While writing this post I have come across a stack overflow discussion page which was useful, you might want to see.

3) GMAPS jQuery Javascript

Generally the above methods should be able to do what you wanted to achieve but in case if you are a web-designer and looking through jQuery based maps, GMaps is one such library for embedding maps in a webpage. You can go through the library at Github for more information. It is very easy to setup and you can read through the documentation to know more about it. Following code is a function call to gMap with different parameters.

$('#map_controls').gMap(
{
     latitude: -2.206,
     longitude: -79.897,
     maptype: 'ROADMAP',
     zoom: 8,
     controls: {
         panControl: true,
         zoomControl: false,
         mapTypeControl: true,
         scaleControl: false,
         streetViewControl: false,
         overviewMapControl: false
     }
});

 4) Old Google Maps

In our previous example of Google Maps, we have seen that the new parameters are origin and destination but previous maps used to have these parameters as “saddr” meaning source address and “daddr” meaning destination address. Following example of HTML code may be helpful for you to get the directions. Note that this has been implemented in a HTML page and you might want to use it an iFrame to embed in a particular page.

<!doctype html>
<html lang="en">
   <head>
        <title>Google Map Directions</title>
</head>
<body>
<form action="http://maps.google.com/maps" method="get">
Enter your starting address:
<input type="text" name="saddr" />
<input type="text" name="daddr"/>
<input type="submit" value="Go" />
</form>
</body>
</html>

As you can see there are many possibilities for a simple requirement of embedding a map into a web page. I hope that above examples are useful for you to provide a starting point for your work. Thanks for reading, good day.

The post How to Add Google Map Driving Directions in your Website ? appeared first on Technophileshub.

Install the AOMEI PE Builder by downloading the software from below link.

http://www.aomeitech.com/pe-builder.html

The complicated process of setting up ADK, installing additional packages and creating a bootable WinPE image is made easy by simple to use graphical user interface of AOMEI PE Builder. All you need to do is select the packages or browse the files that you want to add and click next to provide you with choices of locations to write WinPE image.

Once you select your choice and click next, you can relax and AOMEI PE Builder will take care of the rest for you and provide a bootable ISO image for you to start working.

The post Create a bootable WinPE ISO/USB using AOMEI PE Builder appeared first on Technophileshub.

If you haven’t installed WinPE on your system you can download and install WinPE by downloading “Windows Assessment and Deployment tool kit” (ADK). This software is essential for us to create a WinPE bootable ISO image. Alternatively you can download the WinPE ISO image from sources on internet.

Let’s see how we can create a bootable WinPE ISO image.

After installing ADK on your machine, run the ADK tool as administrator and run the command

copype amd64 c:WinPE

The above command creates a directory containing a standard set of Windows Pre installation Environment (Windows PE) files. We use these files to customize images and create bootable media.

We can verify the directory the above command created at “C:WinPE”. This command creates a “WinPE” directory with 3 sub directories with names “mount”, “media” and “fwfiles”. “media” folder contains all the necessary files for creating WinPE ISO image.

Since the goal of this exercise is to capture an operating system. We need not add any additional packages or features that WinPE allows us to do.

So let’s create a simple WinPE image. This can be done using the command

makewinpemedia /iso "C:WinPE" "C:WinPEWinPE64.iso"

Now you can use the ISO image at “C:WinPEWinPE64.iso” to burn onto a CD/DVD or alternatively can copy the files of this ISO image into a bootable USB partition.

Creating a Bootable USB drive

Now let us create a bootable USB drive for the WinPE ISO image that we have just created. Open up the command prompt by typing “cmd” in runbox.

Plug in the USB device and open up the diskpart by typing the following command

diskpart

It opens up the Microsoft diskpart utility using which we can manage the volumes attached to our machine.

List all the volumes connected to the device using the following command

list volume

Now select the volume of the USB in which you want to create a bootable ISO image using the command

select volume 5

*Please be noted that the volume number will differ in your system.

As we have selected the volume, let us clean the volume for removing any previous MBR or GPT partition data using the command

clean

Now lets create a primary partition in the volume using the command

create partition primary

unlike previous volumes, partitions start numbered from 1. To verify lets list partition using list partition and select the only partition that we have created as follows

list partition

select partition 1

Now let us make the partition active so that BIOS or EFI can recognize our partition as a valid system partition and quick format the drive using NTFS file format.

active
format fs=NTFS quick

Lets assign a letter to the drive so we can copy our WinPE files onto the drive.

assign

Once you have copied the WinPE iso files onto the USB drive. Pendrive is ready to boot.

Following is the summary of list of commands we have used.

list volume
select volume # //where # is the volume number of USB drive
clean
create partition primary
select partition 1
active
format fs=NTFS quick
assign

Please let me know your comments/feedback in comments section.

The post Create a WinPE Bootable ISO image / USB drive appeared first on Technophileshub.

• WordPress themes are modularly developed by splitting the code into multiple template files.
• These template files will have a targeted purpose with a unique name.
• style.css, header.php, footer.php, index.php, single.php, sidebar.php, comments.php …, are some of the template files in a WordPress theme.

Pr-requisites:

• HTML, CSS, PHP
• Text Editor ( I will be using Sublime Text )
• Local WordPress Installation
• WordPress Theme Structure

Theme Structure

There are many other template files like page.php, 404.php, archive.php that I did not mention in the above image because a theme can be developed without having these template files but the two important template files that we should have are “index.php” and “style.css” without which WordPress will not allow to proceed any further. Hope you are geared up for coding these files, let us begin

Theme Development

Create a new folder inside of your “/wp-content/themes/” folder and give it a name (generally theme name). This folder will contain all your theme files like images, scripts etc. Now, create the two important template files “style.css” and “index.php” inside this folder. After creating these two important template files if you look at Themes list in WordPress Dashboard at “Appearance->Themes”, you will find that your new theme is not being displayed, this is because of the fact that WordPress reads any theme information by the declaration maintained in theme Stylesheet(style.css)  which we did not maintain yet. This declaration has a specific syntax and following snippet is a sample of such declaration

/*
Theme Name: Basic Theme
Theme URI: http://technophileshub.com/?p=1575
Author: Pavan Kumar
Author URI: http://technophileshub.com/about/
Description: A basic WordPress theme
Version: 1.0
License: N/A
License URI: N/A
Tags: basic theme
 
Theme developed to demonstrate wordpress theme development at technophileshub
*/

Please go ahead and maintain this declaration in your “style.css” file of your theme. After defining this declaration, if you refresh the Themes list, you will find your new theme with the given Theme Name in Themes list.

Probably if you notice, the new theme is not showing any logo or image while displaying the theme list, this is because we did not maintain any “screenshot.png” image file in the theme directory which WordPress will need to display the image in this list. Never mind, let’s go ahead and activate our new theme. If you look at your blog, Now you are running your blog on a theme that you have created. Yay !!!, our new theme is live but as we haven’t written single line of code a blank page will appear.

Now it’s time for some real coding but nothing to be worried, we will work in a series of progressive steps from top to down of a page and understand every line of code that we are writing. So, let’s begin with header.php template file.

header.php Template File

I believe I need not explain what is header of a webpage and what does it contain as most of us are already aware of this and this is no different than what you already know. header.php is a template file that contains the code written for header section of your blog. It is not a strict rule that you have to maintain only header part of your blog in header.php file but to leverage the full potential WordPress, it is good to put the code in header.php that is common for every page of your theme like Logo, Navigation menu’s etc. After all that’s the purpose of having these template files than individual page where we repeat our code. Isn’t it ?

There are many things that go into header file but since we are focused on creating only a theme, Let’s make it simple. Following is the snippet for a basic header.php file

<!DOCTYPE html>
<!--[if IE 7]>
<html class="ie ie7" <?php language_attributes(); ?>>
<![endif]-->
<!--[if IE 8]>
<html class="ie ie8" <?php language_attributes(); ?>>
<![endif]-->
<html <?php language_attributes(); ?>>
<head id="#" profile="http://gmpg.org/xfn/11">
    <meta charset="<?php bloginfo( 'charset' ); ?>">
    <meta name="viewport" content="width=device-width">
        
        <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
    <title><?php wp_title( '|', true, 'right' ); ?></title>
    <link rel="pingback" href="<?php bloginfo( 'pingback_url' ); ?>">
    <!--[if lt IE 9]>
    <script src="<?php echo get_template_directory_uri(); ?>/js/html5.js"></script>
    <![endif]-->
    <?php wp_head(); ?>
</head>
<body <?php body_class(); ?>>
    <div id="page-wrap">
        <header id="header">
            <h1><a href="<?php echo get_option('home'); ?>/"><?php bloginfo('name'); ?></a></h1>
            <div><?php bloginfo('description'); ?></div>
        </header>

To explain the code written in header,

• First line is basic Document type declaration for HTML5 document type.

• From line number 2 to line number 7, we have conditional comments to identify Internet Explorer browser so that we can write IE specific CSS based on ie7 and ie8 classes declared. You can learn more about conditional style sheets in a blog post by Chris at CSS-Tricks.
• language_attributes(); is a PHP function by WordPress which will return HTML tag language attributes, in my case it will return “en-US” .
• Then we have our head with important meta tags for Charset and Viewport.
• bloginfo( $show ); is a WordPress function that takes a keyword($show) as input and returns the blog information based on keyword used.
• wp_title(); is a wordpress function that will help us to use different titles for different pages of wordpress theme.
• wp_head(); is an essential action hook usually inserted in header of a wordpress theme.
• body_class(); helps us style better with CSS. You can read more about the classes that it assigns for body tag at wordpress codex page for body_class.
• get_option('home') returns the URL for home page.

These are very basic lines of code that will go into header of our blog page. Now, Let’s create a  header.php file and paste the code from above snippet into that file. To test these changes we still need to write one line of code

in our “index.php” file for our code to trigger. Write this one line in index.php and open your blog home page, you must see title of your blog with hyperlink and a description below.

I hope you are with me, I understand that I have introduced many wordpress functions in a single go but can’t help it. Now let’s finish our blog home page from where we have left and then take a look at individual post page.

index.php Template file

index.php is the template file for your blog home page and generally displays the list of blog posts (THE LOOP) with header, footer and sidebar. As of now, we have written only one line of code, which will call the header code from our index.php file. Now we are developing index.php to output blog posts and call functions to display template files for sidebar and footer. Following is the snippet for index.php file

<?php get_header(); ?>
    <?php if (have_posts()) : while (have_posts()) : the_post(); ?>
        <article <?php post_class() ?> id="post-<?php the_ID(); ?>">
            <h2><a href="<?php the_permalink() ?>"><?php the_title(); ?></a></h2>
            <div class="entry">
                <?php the_content(); ?>
            </div>
        </article>
    <?php endwhile; ?>
    <?php else : ?>
        <h2>Not Found</h2>
    <?php endif; ?>
<?php get_sidebar(); ?>
<?php get_footer(); ?>

Paste the above snippet which is called as WordPress Loop  in the index.php file of your theme folder. For the purpose of conceptual clarity, I want to say

<?php get_header(); ?>
<?php if (have_posts()) : while (have_posts()) : the_post(); ?>
//POST content
<?php endwhile; ?>
<?php else : ?>
<h2>Not Found</h2>
<?php endif; ?>

is exactly same if we write as

<?php
if ( have_posts() ) {
while ( have_posts() ) {
the_post();
//
// Post Content here
//
} // end while
} else{ ?>
<h2> Not found </h2>
<?php
} // end if
?>

where have_posts() is a boolean function which will return true if there are any more posts to fetch else it will return false.

While looping through the posts we are using post_class() and the_ID() functions of WordPress to take advantage of CSS styling.

the_permalink(), the_title() and the_content(); will return article link, article title and article content respectively.

get_sidebar(); and get_footer(); will fetch the code in the template files of sidebar(sidebar.php) and footer(footer.php) respectively.

With this we are done with index.php, We now have only 3 more template files single post, sidebar and footer.

sidebar.php Template file

Generally in WordPress, you will control the sidebar section of your blog by using widgets. These widgets dynamically will be loaded onto sidebar section but for that Sidebar section to be there in your widgets section, you need to register sidebar with WordPress.

Create a file with name “functions.php” in your theme folder and paste the following snippet of code

<?php
if (function_exists('register_sidebar')) {
        register_sidebar(array(
            'name' => 'Sidebar Widgets',
            'id'   => 'sidebar-widgets',
            'description'   => 'These are widgets for the sidebar.',
            'before_widget' => '<div id="%1$s" class="widget %2$s">',
            'after_widget'  => '</div>',
            'before_title'  => '<h2>',
            'after_title'   => '</h2>'
        ));
    }
?>

Now let us have these dynamic sidebar widgets in our sidebar section. Copy the below snippet into sidebar.php file, it will show the dynamic sidebar if any is in use

<aside id="sidebar">
<?php if (function_exists('dynamic_sidebar') && dynamic_sidebar('Sidebar Widgets')) : else : ?>
//Content for if no dynamic sidebar widgets goes here
<?php endif; ?>
</aside>

functions.php is theme functions file where you can write your essential function declarations in this file. This functions.php file will be executed before any of our other theme files can be executed. In the above snippet we have used only three wordpress functions

• function_exists('register_sidebar') which will return a boolean value of true if the mentioned function declaration exists.
• register_sidebar(array()) will register our dynamic sidebar widget.
• dynamic_sidebar('Sidebar Widgets') will be calling our dynamic sidebar.

Now let us quickly finish our footer section and see how our blog looks like

footer.php Template file

Similar to sidebar section you can chose to have dynamic widgets for footer with the section split into multiple columns. Here for the simplicity, I am going to insert only Credit links without any dynamic widgets.

        <footer id="footer">
            <small>©<?php echo date("Y"); echo " "; bloginfo('name'); ?></small>
        </footer>
 
    </div>
 
    <?php wp_footer(); ?>
</body>
 
</html>

• echo date("Y"); echo " "; bloginfo('name'); returns the Year and Blog name to display.
• wp_footer(); is the footer hook. We must always use this hook before we are closing the body tag because there are many other plugins that will use this footer hook to insert code.

So, these are all the basic things that we need to set up to create a WordPress theme, If you have followed me through the post, your theme must be looking something like below.

There are plenty of other things that we can do to improve our theme but you can consider that these are the important files that needs to be in place for our theme to work. In the next post, let us add the remaining template files to the theme and take a look at CSS to design our blog UI.

Download Source

The post Create your own wordpress theme from Scratch – WordPress Development Tutorials appeared first on Technophileshub.

Step by Step

• Open your Eclipse IDE, It will open Workspace Launcher window asking for folder path of workspace. Workspace is the location where all your projects files will be stored and optionally you can set this as default location for your workspace.

• As you continue, It will open up the ADT Welcome message which includes tutorial links from Android Developers blog and a button for starting your first Android Project.

• Let’s go ahead and close the window and “Reset the Perspective” from “Window” menu so that all of us are on the same page.

• Now select “New Android Application Project” from “File->New” to Create an Android Project

• It will take you to “New Android Application” Project screen where in you need to provide

Since it is your first Android Project, you need not worry about these options for now and provide any details and click next to continue.

• Once you click on Continue you will be taken to Project Configurations page where you have options for Custom Launcher Icon, Activity and other options like making this project as library or adding the project to existing worksets. For now just click on next to continue.

• As we have selected the option for creating “Custom Launcher Icon”, It will take us to the “Custom Launcher” icon configuration page where you have to provide the Application logo path.

• Keep note of this MDPI, HDPI, XHDPI & XXHDPI, we will talk more about these different DPI’s in the next blog post. After this step the next step is Creating an Activity. As per Android Developers page

An Activity is an application component that provides a screen with which users can interact in order to do something, such as dial the phone, take a photo, send an email, or view a map. Each activity is given a window in which to draw its user interface. The window typically fills the screen, but may be smaller than the screen and float on top of other windows.

• At this stage think of an “Activity” as the Screen that you see on your mobile, we will learn more about Activities in future blog posts. In the screen that you have provided with, there are 3 different options

• Blank Activity – Contains only Action & Navigational Elements.
• Full screen Activity – Hides System UI and Action bar but toggles when you hover.
• Master/Detail Flow – Creates two different Activities with two columns. Best suited for tablets and requires minimum SDK version of 11.

• Click “Next” selecting “Blank Activity” this will take you to, one last and final step, where you need to provide “Activity Name” and “Layout Name” for the Activity that you just have created. By Layout Name we are referring to an XML file that provides the layout for the “Activity” that you have created.

That is all we need to do create our first Android Project. As soon as you click on Finish, ADT will open the Activity layout file “activity_main.xml” and the “MainActivity.java” files allowing you to start developing. Now you can directly test the Application you have created by running the application on Virtual Device that we have created as per the earlier post or on the Physical device that you have with you. In some cases you might need to Run Configurations first to run your application. Please comment below if you have any queries/suggestions.

The post Creating your First Android Application / Android Project appeared first on Technophileshub.

In a traditional HTML page, you write your complete code in a single file other than the CSS but in the case of WordPress, it splits the code in that single page into multiple template files based on the page structure and below is a typical structure of a WordPress page.

Templates are nothing but pieces of a page and WordPress combines them at run time based on query strings in the URL while trying to open a page to create a complete page. Above is the structure of a typical WordPress page which will be rendered by multiple template files. Template files are not just the random pieces of a page but are very specific and have their own purpose with a unique template name. Following are few template files of a WordPress theme for us to get started.

1. Front Page
   • index.php
     The root of any directory is powered by index file and it is also same with the case of WordPress. Your theme root directory contains this index file and will be the first one to be loaded.
   • front.php
     This file if defined will take precedence over index.php to be displayed as front page of your blog or website.
2. Basic building blocks
   Header, Footer and Content page are basic building blocks of WordPress as they are common for every WordPress page.
   • header.php
     Header file contains the code up to the top head section of the page and is written in header.php file and will be called from a content page./li>
   • Content Page (index.php, single.php, page.php)
     These files are content section of your wordpress page. It is up to you to decide what you want to do in content section. For example index.php contains Sidebar and “The Loop” of wordpress which is responsible to display the list of posts. single.php is a single post page which includes sidebar and a section to display the post which also contains the comments section.
   •  
   • footer.php
     Footer is the bottom section of your page which includes copyright, credits and important link details. header.php and footer.php are the only two files that will be called on every page.
3. Single Post Page
   • single.php
     The purpose of this file is to display the content of your post in the content section and you may chose to have a sidebar or opt for full page content. Generally, it calls the template files for both sidebar and comments and finally ends by calling footer.
   • page.php
     This is the template file for your pages in wordpress. As usual, it is up to you to decide how you want to display pages in your wordpress theme. Generally, a page contains header and footer without sidebar or comments section.
4. Multiple Posts Page
   • category.php
     The purpose of this file is to display the posts filed under the specific category.
   • tag.php
     The purpose of this file is to display the posts filed under the specific tag
   • archive.php
     The purpose of this file is to display the archived posts
   • search.php
     The purpose of this file is to display the search results of a query raised in the search form.
5. Comments Page
   • comments.php
     The purpose of the file is to display the comment form and comments filed under a particular post.

These individual template files helps WordPress to work in a modular way. We will discuss more about these files in the future posts when we are actually working on them and for now I am wrapping up this post. Thanks for reading.
Source: WordPress Codex
DZFFQKVR9XKS

The post WordPress Development Tutorials – Theme Structure Theory appeared first on Technophileshub.