Tag

momizat

Browsing

WordPress Themes PHPMyAdmin – or PMA – is an excellent free, open source web-based database client which can be used to interact more easily with MySQL and WordPress databases. I’ll describe how to install it, secure it and some common scenarios with which it can assist you in WordPress administration. Here’s an online demo of PMAfor you to explore.

In addition to offering a visual GUI for database operations, I also appreciate being able to run command line SQL operations via my browser without having to log in to the server via SSH. For example, some WiFi and mobile connections regularly terminate persistent SSH sessions, making database tasks problematic.

Getting started with PMA is fairly straightforward on Linux. I’ll describe how to do so with Ubuntu 14.x at Digital Ocean. Log in to your server via SSH:

apt-get install phpmyadmin

You can use the default settings during installation or customize them to your liking.

On a typical WordPress installation, there aren’t any direct ports to MySQL for a hacker to try to access. They might try to break in via SSH or try SQL injection attacks against WordPress, but they can’t directly attack the database. Once you install PMA, anyone can run web-based attacks against it in order to gain control of your database, so care is warranted.

There are a few precautions I recommend when configuring PMA.

1. Use very strong passwords for all of your MySQL accounts, especially the root account. e.g. 25 characters for the root password.

2. Use different MySQL accounts and privileges for each WordPress site running on a single server. This way if one WordPress password is compromised, only one site’s database is compromised.

3. Change the default URL used by PMA. This way people can’t visithttp://yourblog.com/phpmyadmin. While this security by obscurity isn’t a very effective technique, it does add some protection.

Add an alias to the apache.conf file:

Reload apache:

service apache2 reload

Then, to access PMA, visit http://yourblog.com/myobscuredpma

If you need to modify your PHPMyAdmin password, you can edit the config-db.phphere:

nano /etc/phpmyadmin/config-db.php

4. Configure Web Authentication for the PMA Site. This will require that you enter an additional password to gain access to PMA, in addition to your database password, like this:

It’s very important to remember that PMA allows you to directly manipulate the WordPress database; that means it’s quite easy to break your WordPress site if you don’t know what you’re doing. It’s especially unwise to apply database scripts from the web unless you understand them completely. Use PMA with great care.

for more: http://code.tutsplus.com/tutorials/installing-and-using-phpmyadmin-with-wordpress–cms-21944

[quote font=”verdana” font_size=”14″ font_style=”italic” color=”#474747″ bgcolor=”#F5F5F5″ bcolor=”#dd9933″ arrow=”yes” align=”centre”]This Demo Content Brought to you by Momizat Team [/quote]

this is tags and keywords : wordpress themes momizat Tutorial wordpress templates

 

How To Contribute To WordPress Themes Community

WordPress is built by volunteers. People from all over the world collaborate to create the core software, write the documentation, provide support, translate WordPress, organize events and generally keep the project running. Individuals work on WordPress in their free time, and companies ask their employees to get involved.

Part of WordPress’ success is that the community consists not only of developers, but of designers, user experience experts, support volunteers, writers, users, accessibility experts and enthusiasts. This diverse input strengthens the project. It also means you have more space to get involved. Whatever your skill set, the WordPress community has room for you.

splash
A bunch of WordPress contributors.

In this article, we’ll talk about the different contributor groups and how you can take part. I spoke with the current team reps and project leads, who have offered advice on how to get started with their contributor groups. But first, why should you get involved with WordPress?

Why Get Involved?

I had a chat with Matt Mullenweg, one of the founding developers of WordPress, about contributing to the project. We started off talking about the mix of people who contribute to WordPress. There are contributors who are sponsored by businesses that use WordPress, such as Automattic, Dreamhost and 10up, and then there are passionate individuals who dedicate their own time to the project.

“People who use WordPress are passionate about open source, want to democratize publishing and like to learn. I would say that’s the number-one biggest characteristic, because contributing to open source, and particularly the WordPress project, is probably one of the best learning opportunities on the Internet.”

matt mullenweg
Matt chats about the future of WordPress at the WordPress Community Summit 2012. (Image:konsobe)

For Matt, this is the greatest benefit you will get from contributing. You get to be part of a large, supportive community that has an impact on the lives of millions and millions of people. Something you do in an afternoon can have an effect on people all over the world.

“You can’t knock on the door at Google and say, “Hey, do you mind if I help you out with your home page? I have some ideas for you.” But you could come to us and say, “Hey, I have some ideas for your dashboard, and here are some patches.””

A number of challenges face the WordPress project:

  • Contributor balance
    Currently, the number of contributors is skewed towards people involved with code. Plenty of opportunities lie in other areas — support, documentation and marketing, for example — but not so many people are getting involved.
  • Mobile
    Not enough people are getting involved with mobile. Most of the people involved with mobile are currently sponsored by Automattic. Because mobile is fast becoming the way that people interact with the Internet, this is a crucial group and currently has a dearth of contributors.

With that in mind, let’s look at the ways you can get involved with WordPress.

Core

Mark Jaquith is an independent developer and one of the lead developers of WordPress. These days, he is a jack of all trades in the project, working closely with younger and newer developers, helping to point them in the right direction. He was also the release lead for the 3.6 release cycle. The core team comprises all sorts of developers and designers — PHP and JavaScript developers and front-end developers and designers. These are the people who build the WordPress that you install on your server.

mark jaquith
Being a lead WordPress developer makes Mark Jaquith happy. (Image: Michael Yoshitaka Erlewine)

I asked Mark how the the core contributor team works. He describes it as a set of concentric rings:

“You have the leads in the inner sanctum, and then you have the people with permanent commit access, and then you have the people to whom we give temporary commit access for release, and then there are the people whose patches are implicitly trusted and go in without too much inspection. It just keeps going out from there. Those are very fluid boundaries, so people flow between them.”

CHALLENGES

As much as possible, the core team tries to work by consensus. Issues are discussed, publicly if possible, although anything contentious may be addressed in private discussion.

One of the biggest challenges facing WordPress is that not everyone is on the project full time. Even Automattic employees have other responsibilities within Automattic. This means that people can contribute varying amounts of time. If a lot of people see a dip in their free time, this can cause problems for the project. The core team tries to mitigate this by having more contributors and more people who can commit. However, a balance has to be struck because if there are too many committers, no one would know what’s going on.

GET INVOLVED

You can start getting involved in a number of ways:

  • Live chats
    Tap into the weekly live chats (Wednesdays 21:00 UTC, irc.freenode.net, #wordpress-dev). Before diving in, you should gauge at what point in the release cycle the project is at:

    • Early stages
      Planning the next release.
    • Middle stages
      Guiding the features and checking on progress.
    • Final stages
      Bug scrubs.
    • After a release
      Mostly an open forum, a good time to ask for advice on moving your ticket forward.
  • Firehose
    You can subscribe to trac notifications and get notified of every comment in every ticket. It’s a lot of data to process, but you should get an idea of how the project works, various people’s roles, how much authority they have, and best practices.
  • Ideas
    If you have an idea for a feature or anything else WordPress-related, a good place to start is to write a blog post about it. There is an ideas forum, but it’s not very well used. If you have a concrete idea, with a vision of how to implement it, a blog post may well get you more traction. It will give you space to flesh out the idea and provide an opportunity for other community members to comment on it.

Ready to get involved with WordPress core? Other than development skills, I asked Mark what skills someone should have:

“The number one skill you need for just about any job, but specifically working on open source, is communication skills. You need to have clarity, consistency, compassion, relatability, a little bit of a thick skin and a decent sense of humor.”

from : http://www.smashingmagazine.com/2014/08/27/a-tour-of-wordpress-4-0/

[quote font=”verdana” font_size=”14″ font_style=”italic” color=”#474747″ bgcolor=”#F5F5F5″ bcolor=”#dd9933″ arrow=”yes” align=”centre”]This Demo Content Brought to you by Momizat Team [/quote]

this is tags and keywords : wordpress themes momizat Tutorial wordpress templates

Final product image
What You’ll Be Creating

Brute force login attacks targeting WordPress sites are quite common, such as in April 2013 when more than 90,000 sites were targeted. There are a handful of good ways to protect yourself against these attacks:

However, I prefer to use a two-factor authentication method that requires a code from my phone to complete the login process. Google’s Authenticator has been gaining ground as a mobile app for providing secure codes. In fact, you may already have the Google Authenticator app on your phone, as a number of web services are now integrating with it, including cloud file store provider Dropbox, cloud hosting provider Digital Ocean, and name service provider Gandi.net.

And, fortunately, there is a simple WordPress plugin by Henrik Schack that integrates with Google 2fa; it’s also called Google Authenticator. Installing and using this plugin is quite easy—and the security benefit is significant.

Google Authenticator WordPress Plugin by Henrik Schacks

This tutorial will walk you through setting up the Google Authenticator WordPress plugin for your own sites.

From your WordPress Dashboard, go to install a new plugin and search for Google Authenticator, and click Install Now:

Install the Google Authenticator Plugin

Then, click Activate Plugin:

Activate the plugin

From the dashboard, click Users > Your Profile and scroll down to the Google Authenticator settings:

Google Authenticator Plugin Settings

Click on the checkbox for Active. Modify the description so that you will recognize the site on your Google Authenticator mobile app and show the QR code.

Note that the plugin works for multiple users—and each user has the choice of enabling it for themselves.

From your mobile Google Authenticator App, click the upper right pen (for editing). Click the plus sign at the bottom for adding a site. Choose to scan the barcode and point your camera at the QR code. The process is quite fast.

Add Your WordPress Site to Mobile Google Authenticator App

Log out of your WordPress site and you should see the additional field for Google Authenticator on your login screen!

WordPress Login with Google Authenticator Two Factor Authentication

To log in, enter your username and password as usual, but visit your Google Authenticator mobile app to get the additional code for logging in. The codes are time-critical and expire every few minutes.

Retrieve your mobile authenticator code to login

Congratulations, you’ve successfully implemented two-factor authentication on your WordPress site.

In writing this tutorial, I was accidentally logged out of my site before I had registered my site with the mobile app. I couldn’t log back in—but luckily, there is a simple solution listed on the plugin support page.

I just had to log in via SSH to my server and change the name of the plugin folder temporarily. Then, I logged back into WordPress, reset the plugin folder name, added my site on my mobile app, and I was good to go.

Another way to do this is through the database using a tool such as PHPMyAdminand these queries. If you’re not self-hosting, you may need to request help from your hosting company.

I hope you’ve found this useful; now go secure your WordPress sites.

Please post any comments, corrections or additional ideas below. You can browse my other Tuts+ tutorials on my author page or follow me on Twitter @reifman.

 

from : http://code.tutsplus.com/tutorials/using-google-two-factor-authentication-with-wordpress–cms-22263

[quote font=”verdana” font_size=”14″ font_style=”italic” color=”#474747″ bgcolor=”#F5F5F5″ bcolor=”#dd9933″ arrow=”yes” align=”centre”]This Demo Content Brought to you by Momizat Team [/quote]

this is tags and keywords : wordpress themes momizat Tutorial wordpress templates

At the recent WordCamp Edinburgh, I took part in a panel discussion about WordPress theme development and the options available to developers when building themes. The overriding conclusion from the session was that there isn’t a one-size-fits-all answer and that the best method depends on the needs of the website and the capabilities of the developer.

But if you’re starting out building WordPress themes or want to develop a system for building them more efficiently or robustly, how do you decide which approach to take? In this article, we’ll briefly describe how WordPress themes work and then look at some of the different approaches to developing them, with tips on which approach might be most suitable for your website and circumstances.

How Does A WordPress Theme Work?

In WordPress, themes drive a website and determine what it contains, how it behaves and what it looks like. The theme is separate from the content, which is held in the database. This means you can use the same theme on more than one website, regardless of the content of the websites — which you might already be doing if you’ve downloaded themes from WordPress’ theme repository.

 

What To Consider When Developing A WordPress Theme?

Before deciding which approach to take to develop your theme, identify your constraints. These likely include the following:

  • Time
    How much time do you have to develop your theme, or to learn how to do it?
  • Budget
    This is related to time but also has to do with whether you can afford to pay for a premium theme or a theme framework.
  • Capability
    How familiar are you with theme development, with CSS and PHP and with how themes work? If you’re not familiar, how much do you want to learn?
  • Future-proofing
    Will your theme need to be updated in future? Will other developers be working on it in addition to you? If so, then your approach will need to be as robust as possible.
  • Repetition
    Do you see yourself developing a number of similar themes in future? If so, your approach will have to allow for code to be reused.

We’ll revisit these considerations at the end of the article and identify which development options are most suitable for various situations.

Theme Development: Your Options

A few options are available for developing your theme or themes, and investigating them before you roll your sleeves up and start coding would be worthwhile. Picking the right approach will result in a better theme, with more robust code, and it will minimize the amount of revisions you’ll have to do later. It will also help you to build the theme more efficiently.

The options we’ll look at here are:

  • Build a theme from scratch,
  • Edit (or “hack,” some might say) an existing theme,
  • Use the theme customizer to tweak an existing theme,
  • Create a child theme to make changes to an existing theme,
  • Create your own parent theme (using one of the approaches above) and child themes,
  • Use a theme framework.

1. BUILD A THEME FROM SCRATCH

This approach is the most difficult if you’re inexperienced. But if you’re a seasoned WordPress developer, it will give you the most control. It might be the most appropriate method if you’re importing HTML from an existing static website that is being upgraded to WordPress with no other changes.

However, when transferring a website to WordPress, conducting a review of it as part of the process, rather than simply copying the code across, is a good idea. If you are copying a static website, you’ll need to keep a close eye on your code to ensure that it’s clean, efficient and valid.

2. EDIT (OR HACK) AN EXISTING THEME

This is how most people start with WordPress theme development: in working on a theme that they’ve downloaded, they see that some styling isn’t quite right, so they delve into the style sheet and make some edits. Starting like this is tempting because it feels like a quick and easy way to achieve the effect you want. But there are some dangers:

  • If you ever switch themes, that update will override any changes you’ve made.
  • It’s easy to add repetitive code by adding new styles lower down in the style sheet that override styles higher up, rather than removing what you don’t need.
  • The website could end up with a lot more code than it needs.
  • If the theme isn’t well coded or commented to begin with, you could get yourself into a bigger mess and find that you have to make a lot of fixes.

However, hacking a theme can work if you go into it with your eyes open. It may be an option if the following are true:

  • The theme you’re using is well written, valid and commented (e.g., the default WP theme, Twenty Eleven);
  • The changes you’re making are so drastic that you wouldn’t need to update the original theme;
  • You understand the PHP and CSS contained in the theme and are comfortable editing, adding to and removing it without breaking the theme.

If you do decide to go down this route, keeping a backup of the original theme and commenting your code thoroughly are important. I would also advise commenting out any code that you don’t want and then testing to see what happens before deleting anything.

3. USE THE THEME CUSTOMIZER TO TWEAK AN EXISTING THEME

The theme customizer was released with WordPress 3.4. It gives you the option to customize a theme without writing any code, simply by using a WYSIWYG interface. Depending on how well the customizer is written into the theme itself, you can use it to change images, titles, colors and even the layout. Expect to see more themes with the customizer integrated into them.

Using the WordPress theme customizer with the Twenty Ten theme.
Using the WordPress theme customizer with the Twenty Ten theme.

The theme customizer stores your changes in a separate file, not in the theme’s style sheet, so there will be repetitive code.

For more information, take a look at Otto on WordPress’ video tutorial or guide to integrating the theme customizer into your own themes.

4. CREATE A CHILD THEME TO MAKE CHANGES TO AN EXISTING THEME

This approach is similar to editing an existing theme, but safer. It consists of creating a brand new theme that is defined as a child of the existing theme. Where your child theme doesn’t have a particular file but the parent theme does, it will use that. Where the child theme does have a file, that file will override the equivalent in the parent. This line tells the browser to load the parent theme’s style sheet before rendering any of the styles in the current style sheet. This frees you from having to duplicate any styles in the parent theme that you want to use.

So, that’s how child themes work. But when is this the best approach? I would suggest using it in the following cases:

  • You already have a theme (to be used as the parent) that contains most of what you need for your theme;
  • You want to be able to update your parent theme (for example, when theme updates are released following a WordPress update);
  • You don’t want to get tied up in knots from hacking an existing theme;
  • You want the option to revert to the parent theme or to develop another similar theme in future (which would be a new child theme);
  • You’re developing a number of similar websites with some minor stylistic or content differences (I did this when building similar websites for a client that owned multiple companies);
  • The difference between your child and parent themes is not so huge that you need to start from scratch, or not so huge that your child theme’s code will override anything affected by updates to the parent theme.

 

from : http://www.smashingmagazine.com/2013/03/13/a-guide-to-wordpress-theme-options/

[quote font=”verdana” font_size=”14″ font_style=”italic” color=”#474747″ bgcolor=”#F5F5F5″ bcolor=”#dd9933″ arrow=”yes” align=”centre”]This Demo Content Brought to you by Momizat Team [/quote]

this is tags and keywords : wordpress themes momizat Tutorial wordpress templates

There is so much to learn about WordPress theme development. The Internet is home to hundreds of articles about building WordPress themes, to countless theme frameworks that will help you get started, and to endless WordPress themes, some of which are beautiful and professional but not a few of which are (to be honest) a bit crappy.

Rather than write another article on building a WordPress theme (which would be silly, really, since any theme I build would fall into the “crappy” category), I’ve asked some of the top theme designers and developers to share some tips and techniques to help you improve and refine your theme development and design process.

Before we get into that, Mark Forrester, cofounder of WooThemes, has shared some insight into his firm’s development process. Given WooThemes’ success, no doubt we can all learn something from it.

A Peek Into Woo

Whether you work in a large theme shop or are a lone designer, you can learn plentyfrom another designer or developer’s workflow.

  1. A theme at WooThemes starts life on the ideas board, through specifications provided by the community or based on a concept that’s emerged from customer research. It is designed either in house or by an industry-leading designer who is hired on contract.
  2. The theme is then meticulously designed in Photoshop. All of the major elements are styled and the pages constructed before any code is touched. Mark recommends Photoshop Etiquette for guidelines on structuring your design file. He says, “The better the Photoshop file, the easier the theme build.”
  3. Once the design is approved, it’s assigned to a developer, who works from WooThemes’ base theme. This includes the templates that come with every WooTheme, along with basic styling. The base theme has a responsive layout, and the CSS is managed using LESS, which Mark strongly recommends.
  4. Theme development is managed with Trello, and milestones are set withTeamGantt.
  5. Once the theme is finalized, the developer creates a demo for the website that is populated with dummy content and that tests almost every element of the design.
  6. The team sets about beta testing the theme. A list of bugs, tweaks and solutions is compiled, a hackathon is scheduled, and everything is completed by the developer.
  7. For WooThemes’ own redesign (which is awesome — congrats, guys!), the team started to use BugHerd, which helped them gather user feedback and track it directly in the pages.
  8. All revisions are included in the change log for easy reference. A strict numbering convention distinguishes between bug fixes and new features.

That’s a lot of process right there. Creating a WooTheme theme is about much more than knocking out a few lines of code. Here’s what Mark has to say:

“When we create and edit our themes it is not simply diving into the code. We have to carefully consider our community of users and how any code might impact their usage, and the template files’ customization ability.”

Apart from workflow, what else can be learned from professional theme designers and developers?

Develop Locally

If you’re not developing locally, then now’s the time to start. Here’s what Chris Coyier has to say about it:

“Designers and developers who work mostly on WordPress sites are, in my experience, the worst offenders of the “just do it live” development system. FTP commandos, if you will. I know — I was one for a lot of years. I suspect it’s the case because there are quite a few requirements to run a WordPress site locally: an Apache server running PHP and a MySQL database.

These things aren’t preinstalled on most computers like they are on most servers. Even if you get over those hurdles, setting up a workflow between local and live isn’t trivial.”

Luckily for you, Chris is going to show you a better way. Developing locally is easy to get started with.

STEP 2: GET OFF FTP

Developing locally has so many benefits. In particular, you’ll be able to do the following:

  • Have a record of everything that has ever changed and when it changed.
  • Roll back mistakes.
  • Become more efficient by using text-editor features such as “Find in Project.”
  • Work on major redesigns without worrying about screwing up a live website.

ALTERNATIVE TOOLS FOR A LOCAL SERVER

Use Live Reload

When you’re developing a theme, switching to the browser and reloading the page gets old pretty fast. That’s why Drew Strojny, founder of The Theme Foundry and the guy behind WordPress’ gorgeous new Twenty Twelve default theme, uses LiveReload:

“LiveReload is a great little application that works through a browser extension. LiveReload automatically reloads your page when a file has been changed in your project.

This is a huge productivity boon when you’re editing and tweaking a WordPress theme. All those small page refreshes add up to a big chunk of time saved at the end of the day. Not to mention, your fingers get a much needed break!”

The Theme Foundry loves LiveReload so much that it’s built support for it into Forge, its free command-line toolkit for bootstrapping and developing WordPress themes.

Use Git

Git is a distributed version-control system that is popular among developers all over the world. The great thing about Git is that you can quickly create a branch, make changes within that branch and then test those changes without affecting the master version. It’s what The Theme Foundry uses for every project:

“Quite honestly, we’d be lost without it. Git makes branching cheap and easy. You can experiment quickly with different ideas without worrying about getting lost. Think of it like the trail of pebbles left by Hansel and Gretel to help them find their way back home.

Git gives you the power to leave nicely annotated pebbles along your development path. If you see something interesting and wander off the trail, but then later change your mind, you can always get back to where you started.”

LEARNING GIT

 

from : http://www.smashingmagazine.com/2013/02/21/wp-theme-development-process/

[quote font=”verdana” font_size=”14″ font_style=”italic” color=”#474747″ bgcolor=”#F5F5F5″ bcolor=”#dd9933″ arrow=”yes” align=”centre”]This Demo Content Brought to you by Momizat Team [/quote]

this is tags and keywords : wordpress themes momizat Tutorial wordpress templates

In case you missed it, WordPress release 3.4 included a very exciting new development: the Theme Customizer. This allows users to tweak theme settings using a WYSIWYG interfaceand customize the theme so it includes the colors, fonts, text — and pretty much anything else — they want.

WordPress 3.4 allows you to make extensive customizations to a theme, including colors, fonts, and text.
WordPress 3.4 allows you to make extensive customizations to a theme, including colors, fonts, and text.

The purists out there may be throwing their hands up in horror — a WYSIWYG interface! Letting users alter themes themselves! Surely that opens the floodgates for the creation of thousands of ugly, messy WordPress websites? Well, yes, there is a risk of that. But more importantly, the Customizer means that if you’re developing custom themes for client websites, or themes for other developers to use, you have a whole new set of tools to play with.

With the Theme Customizer:

  • If you’re developing free or premium themes for others to use, integrating the Customizer will make your themes much more appealing to developers and website owners.
  • If you’re building client websites, you can let your client tweak the template content of their website such as the logo, tagline and contact details in a more intuitive way than by using a theme options page.
  • For both groups, you can let website users and developers make changes without having to rely on widgets or theme options pages — a less risky and less time-consuming approach.

So, let’s start by having a look at what the Theme Customizer is and how it works for the user.

How The Theme Customizer Works For Users

The Theme Customizer has been integrated into the Twenty Eleven Theme, so you can try it out using that theme. There’s a great video on the Ottopress blog showing you how the Customizer works with Twenty Eleven. Using it is simple:

  1. On the “Themes” page, search for and activate the Twenty Eleven Theme.
  2. On the same page, click on the “Customize” link under the current theme’s description.

The “Customize” link is right below the current theme's description on the “Themes” page.
The “Customize” link is right below the current theme’s description on the “Themes” page. Larger view.

  1. This brings up the Theme Customizer in the left column, along with a preview of your website on the right.

The theme customizer shown with the twenty eleven theme
The Customizer options are shown side-by-side with a preview of your website, so you can test the effect of changes. Larger view.

  1. To make changes, all you have to do is select each of the available options and edit their settings. The options are:
    • Site title and tagline
      Edit the title and tagline of the website without having to go to the “Settings” page.
    • Colors
      In the Twenty Eleven theme, you can only change the color of the header text and website background, but as we’ll see, this can potentially be used for much more.
    • Header image
      Choose from one of the default images or remove the header image altogether.
    • Background image
      Upload an image to use as the background of the website. The image below is what happens when I upload an image of some hang gliders to my website. The image can be tiled but unfortunately doesn’t stretch.

You can set your background image to tile, but not stretch.
You can set your background image to tile, but not stretch. Larger view.

    • Navigation
      Select which menu you want to use for the primary navigation of your website.
    • Static Front Page
      Specify whether the front page of the website should be a listing of your latest posts, or a static page of your choosing.
  1. Once you’ve made the changes you want, you must click the “Save & Publish” button. Until this is clicked, none of the changes are reflected in the live website. This means you can play to your heart’s content without your visitors seeing your experiments.

Another really exciting way to use the customizer is when previewing themes. If a theme has the Customizer built in, you can use it to make tweaks before downloading and activating the theme.

This demonstrates the Customizer in action with the Twenty Eleven theme, but what about your own themes? How would you harness this to add more functionality in themes you are selling or developing for clients?

So let’s take a look at how to implement Customizer in your theme, and how to add your own customization options.

 

 

from : http://www.smashingmagazine.com/2013/03/05/the-wordpress-theme-customizer-a-developers-guide/

[quote font=”verdana” font_size=”14″ font_style=”italic” color=”#474747″ bgcolor=”#F5F5F5″ bcolor=”#dd9933″ arrow=”yes” align=”centre”]This Demo Content Brought to you by Momizat Team [/quote]

this is tags and keywords : wordpress themes momizat Tutorial wordpress templates

The theme framework you’ve built will be used as a parent theme in the sites you develop. This means that in each case you’ll need to create a child theme to create a unique site with its own design and with extra or different functions compared to the framework.

The obvious way to go about this is to dive in and start creating template files in your child theme to override those in the framework, but thanks to the action and filter hooks you’ve added to your framework, this might not always be the best approach.

In this article, I’ll outline some of the techniques you can use in your child themes to make best use of your framework and improvise your workflow.

The topics I’ll cover are as follows:

Creating starter child themes
Amending code via the framework’s filter hooks
Adding code via the framework’s action hooks
Creating template files in your child theme
When to use a plugin instead
Creating Starter Child Themes framework

The main purpose of developing your theme framework is to adopt the DRY (Don’t Repeat Yourself) principle, and that applies to your child themes, too.

It can make you more efficient if you create one or more ‘starter’ child themes for use with your framework, which contain the core code you need to get started on new projects.

When deciding how to go about doing this, consider the way you work and the sites you build:

Do you create a lot of sites for clients in the same sector with similar needs?
Do you want to offer low cost template based sites to smaller clients?
Are there specific template files you tend to create for most of your new projects?
Is there functionality you need to include on some sites but not others? (For example, I use two starter child themes, one with comment functionality and one without.)
Is there styling you tend to use for most projects, or can you use object oriented styling or a CSS preprocessor for most projects?
Are there libraries or resources you use for most new projects, or for a significant proportion of them?
Do you have two or three main categories you can place projects under, with each category involving similar development work?
If you’ve answered yes to any of these questions, then developing one or more starter child themes may save you time. You can create a set of child themes with the basic code that you repeat across all projects using them, and then you don’t need to rewrite that code (or create those files) for each new project.

Note on caveat: If you’re adding some code to every single new project, you may want to add it to your framework instead of to child themes, maybe by using a hook so you can override it if a different need arises in the future.

Even if you answered no to the questions above, it’s worth creating a very basic starter theme with an empty stylesheet and functions file, and adding the instructions WordPress needs to access your framework’s parent theme .

You might also want to create a starter functions.php file with the functions you most frequently use in your child themes. You can then choose to remove any of these and/or add to them for specific projects.

Amending Code via Filter Hooks

As well as adding styling to your child theme, you’ll most likely want to make changes to the code output by the framework. The most lightweight way of doing this is via filter hooks, so it’s worth exploring those first to identify if you can use any of them.

Creating a function which you then attach to a filter hook is much more efficient than creating a whole new template file for the new code; however, if you find yourself doing this repeatedly with the same filter hook, you might want to consider changing that filter hook to an action hook and writing a new function for each project which you activate via that action hook.

To be more efficient, you might want to create a set of relevant functions which you place in the functions file of different start themes or even create a plugin with your function which you activate when needed. I’ll cover plugins in more detail later in this series.

Adding Code via Action Hooks

Your theme framework will also have action hooks which you can use to insert content in various places in your sites.

If you’ve been working on the code files for the framework bundled with this tutorial series, you’ll have seven action hooks to work with:

before the header
inside the header
before the content
after the content
in the sidebar
in the footer
after the footer.
To do this, create a functions.php file in your child theme and .

There is plenty of other content you could add using your action hooks, such as sharing buttons above or below the content, extra content in the footer, a search box in the header and much more.

You might just want to add some content on specific page types, such as single blog posts, in which case the most obvious place to start would be by creating a newsingle.php template. But you can still use your action hooks with the addition of a conditional tag.

Creating New Template Files

On occasion you won’t be able to do what you want using the filter or action hooks in your framework, in which case you’ll need to create new template files in your child themes.

These might be the same template files as are stored in your framework, in which case the files in the child theme will override them. Or they might be new template files, for example for a new category, taxonomy or post type.

If you are creating template files in your child themes, it makes things easier if you use the template files in your framework as a starting point. The steps I follow are:

Identify the template file you need to create with reference to the WordPress template hierarchy
Create a blank file with the appropriate name in your child theme
Identify the file in your framework which is closest to the new file (again with reference to the template hierarchy)
Copy the contents of that into your new file
Make amendments to the new file as required.
Doing this saves you the work of duplicating any code which will be common between your new file and the existing files in your framework, such as the calls to include files.

When to Use a Plugin Instead

Another option you have when creating sites based on your framework is to use plugins in conjunction with your child themes. A plugin won’t replace a child theme completely, but it can be useful in the following circumstances:

The functionality you want to add isn’t theme-dependent (i.e. you want to keep it if the site ever changes theme in future). This might include registering custom post types or taxonomies, for example.
You want to use this functionality on a number of the sites you create, but not enough for it to go into a starter child theme or the framework itself.
I’ll cover developing plugins for your framework in the next part of this series.

Summary

Your theme framework is just the starting point of a library of code and files you’ll create to support the sites you develop. Each site you create will need to run on a child theme, which will have your framework theme as its parent.

As we’ve seen, your child themes will add their own styling and functionality, and they can do this by hooking into the action and filter hooks in your framework, or via the creation of new template files. It’s always a good idea to adopt the solution which needs the least code, as that makes your site faster and your life easier!

from :http://code.tutsplus.com/tutorials/creating-child-themes-for-your-wordpress-theme-framework–cms-21933

[quote font=”verdana” font_size=”14″ font_style=”italic” color=”#474747″ bgcolor=”#F5F5F5″ bcolor=”#dd9933″ arrow=”yes” align=”centre”]This Demo Content Brought to you by Momizat Team [/quote]

this is tags and keywords : wordpress themes momizat Tutorial wordpress templates

 

You have to change you timezone, the tagline, your user profile information, and much more.

Perhaps one that setting that needs to change but that has stumped quite a few is the Permalink setting. You are given quite a few options there, but which one is the best to use?

What Is A Permalink?

To those new to the realms of the online world, the word Permalink likely doesn’t make any sense, but it’s not that complicated.

A Permalink is like the exact address to a specific page on your website. For example:

http://yourwebsite.com/ would bring someone to the Homepage of your site whereas,http://yourwebsite.com/blog/ would bring them to your the blog page on your site. Those are pretty straightforward permalink structures, but when it comes to posts on your site, the permalink structure may look a little bit different.

Permalink Options in WordPress

WordPress gives users a few options when choosing a permalink structure:

  • Default
  • Day and Name | Uses the year, month, and the day along with your post title in the link.
  • Month and Name | Uses year and month along with the post title in the link.
  • Numeric | Uses a number as part of the link.
  • Post Name | Simply uses the title of your post in the link.
  • Custom Structure | Allows you to set up your own link structure to reflect something closer to what you’d like.

As you can guess, many WordPress installs have the Default setting automatically put in place, but it’s not one you want to leave as is.

Which Permalink Structure is Best?

In this case, there is no single answer, though some may have strong feelings about one structure over another. What I can tell you is that you shouldn’t use the Default option. So which one should you use?

Post Name

This is the one that many people like to choose as their permalink structure. This option is nice for both Search Engines and your viewers as the link is very easy to understand because it uses the post title. Since Search Engines can read this plain as day many people like to say that it has SEO benefits.

If you decide to go with this one, you’d be just fine.

Day and Name; Month and Name

These two options are pretty similar, however, the Day and Name option will make your permalink a bit longer than the Month and Name option. This isn’t exactly a bad thing so you can choose one over the other and be all set.

There are some hidden benefits to using these structures. Besides creating these “Pretty Links” that flirt rather well with Google, they also help keep a site from breaking if your site publishes multiple posts every day (Day and Name is best for news type sites with daily/hourly updates). If you publish quite a few posts every week, the Month and Name option would likely be your best option.

Wrapping It Up

As far as SEO is concerned, one structure doesn’t seem to do any good over another. Although Post Name is a nice and simple option, I’d opt for either the Day and Name or Month and Name option just to keep things going smoothly. If you’re feeling adventurous, you could even try out the Custom Structure option like some popular blogs use.

If you want more in-depth coverage of Permalinks, be sure to check out this post byKevin Muldoon.

 

 

from :http://code.tutsplus.com/tutorials/creating-child-themes-for-your-wordpress-theme-framework–cms-21933

[quote font=”verdana” font_size=”14″ font_style=”italic” color=”#474747″ bgcolor=”#F5F5F5″ bcolor=”#dd9933″ arrow=”yes” align=”centre”]This Demo Content Brought to you by Momizat Team [/quote]

this is tags and keywords : wordpress themes momizat Tutorial wordpress  templates

Getting your readers to return to your blog is something that every website owner has to get to grips with at some point. At times it can be a constant battle to drive that returning traffic. Then there’s the problem of keeping your readers interested when they get to your site.

Wouldn’t it be great if you could improve your website’s traffic flow and frequently update your website, with very little work?

It sounds too good to be true doesn’t it?

This is a sponsored review, it is completely impartial and not influenced in any way by being paid. If you would like to order a sponsored review, please visit our advertising page.

Anything that takes little effort, has to have a catch – it’s the way the world works. And yet here I am, about to share a WordPress plugin with you, that may just do that very thing.

get-events-plugin

Today I’m introducing GetEvents, a plugin that claims to do all of the above. I have to say I’m always a sucker for jumping on anything that says it will improve my site’s level of returning traffic, so how about we give it the benefit of the doubt and see what it has to offer first.

GetEvents For WordPress

GetEvents is a platform that helps people to find events wherever they are in the world. Via the installation of a simple plugin, you can quickly and easily create a page on your website dedicated to events that are happening in a location of your choosing.

Users can browse events based on the parameters you choose in your settings. For example if you’re a tech blog, you can choose to display tech events. Restaurants and hotels can display events happening in their local area for tourists to discover.

get-events-2

You can also display your own events by adding it to your GetEvents login area. Your event will display alongside others in the area you select, helping to drive engagement and add variety to your listings.

Because GetEvents always has the latest content, it can provide great benefits for your website’s level of returning visitors. Your website will always have regular updates in the form of event listings, with content that people are looking for which ensures people will continue to come back to your website to check for updates and create a buzz around your site.

With this in mind, let’s take a look at GetEvents in more detail. I’ll walk you through creating an account, getting the plugin set up and creating your first GetEvents page for your WordPress website.

GetEvents Plugin Review

The GetEvents plugin is currently free to download and install. Head to the GetEvents plugin page which can be found in the WordPress.org plugin directory, and download the plugin to your hard drive.

get-events-1

From within your WordPress dashboard, navigate to Plugins and Add New. Browse your hard drive for the GetEvents .zip file and click Upload. Finally activate the plugin.

get-events-5

To view the GetEvents settings area, select GetEvents from the left navigation area of your WordPress Dashboard. At this stage you’ll be asked to either create an account or login with your existing details.

get-events-6

Creating an account is simple. Type in your Website, Email, Name and Password, then click Create Account. Be sure to check your emails for your confirmation message and to successfully activate your installation.

get-events-7

Once you’ve logged in, you should see a screen similar to the one above. This is your GetEvents plugin dashboard and it’s where you can set up your first events page. As you can see there’s a piece of example text to show you the type of thing you could add to your page. Go ahead and change this to a location of your choosing.

For this review I’ve chosen to set my location as Event In London. Once you’ve chosen your location, click the Add Page To WordPress button. The plugin will now automatically create a draft page where your events listing will appear when published.

get-events-8

In the screenshot above you can see there are further fields you can now fill in. These include:

  • Sub-Title – here you can explain a little further about the types of events you’ll be listing on the page for example.
  • Add Keyword – this field is self-explanatory and allows you add the main keywords associated with the events you’d like to list.  Example keywords could be; ‘London Events’, ‘Days Out London’ or ‘Tech Events London’’.

get-events-9

With the GetEvents plugin you can further customize the look of your events page. Clicking either Background, Header or Link will bring up a color picker tool. Here you can change the colors of the respective elements, enabling you to match your page to your website’s branding.

 

from :http://code.tutsplus.com/tutorials/creating-child-themes-for-your-wordpress-theme-framework–cms-21933

[quote font=”verdana” font_size=”14″ font_style=”italic” color=”#474747″ bgcolor=”#F5F5F5″ bcolor=”#dd9933″ arrow=”yes” align=”centre”]This Demo Content Brought to you by Momizat Team [/quote]

this is tags and keywords : wordpress themes momizat Tutorial wordpress  templates

Are you using Jetpack’s publicize feature on your site?

Recently while browsing through Facebook, we found several folks sharing links where WordPress replaced the site domain. Along with that, the status also read like this: Michelle Schulp published an article in WordPress.

<img class=”alignnone size-full wp-image-25095″ title=”Facebook Status being hijacked by JetPack publicize” src=”http://cdn.wpbeginner.com/wp-content/uploads/2014/12/fbstatusjetpackpublicize.jpg” alt=”Facebook Status being hijacked by JetPack publicize” width=”520″ height=”479″ />

This was alarming, so we decided to investigate the issue.

When you click on the link, it takes you the website. However when you click on WordPress, it takes you to a WordPress.com signup page on Facebook.

<img class=”alignnone size-full wp-image-25087″ title=”Landing page for WordPress.com’s app” src=”http://cdn2.wpbeginner.com/wp-content/uploads/2014/12/wordpresscom-app.png” alt=”Landing page for WordPress.com’s app” width=”520″ height=”286″ />

We looked further to see if these sites were hosted on WordPress.com, a blog hosting service. Most of them weren’t. (see the <a title=”Self Hosted WordPress.org vs. Free WordPress.com [Infograph]” href=”http://www.wpbeginner.com/beginners-guide/self-hosted-wordpress-org-vs-free-wordpress-com-infograph/”>difference between free WordPress.com vs self-hosted WordPress.org</a>)

However, they all had one thing in common. All of them were using the Jetpack plugin which is created by the parent company of WordPress.com, Automattic.

In order to verify our findings, we decided to install Jetpack on a test site. We replicated the issue, and it is connected with the publicize feature of the plugin.

When setting up the publicize feature, you are asked to connect with Facebook and grant several permissions.

<img class=”alignnone size-full wp-image-25082″ title=”Facebook permissions for using Publicize feature in JetPack” src=”http://cdn.wpbeginner.com/wp-content/uploads/2014/12/facebook-permissions.png” alt=”Facebook permissions for using Publicize feature in JetPack” width=”520″ height=”390″ />

<img class=”alignnone size-full wp-image-25083″ title=”Allowing WordPress.com to post on Facebook for you” src=”http://cdn2.wpbeginner.com/wp-content/uploads/2014/12/post-to-fb.png” alt=”Allowing WordPress.com to post on Facebook for you” width=”520″ height=”367″ />

During the permission process, you see the blue W logo instead of the grey W logo. How is that different?

Well, one is for WordPress.com (the blog hosting service) and the other is for WordPress.org (the software that we all come to love and use).

Confusing isn’t it.

Often beginners do not know the difference, so they think they’re really authorizing their WordPress site, not a third-party WordPress.com platform (see <a title=”How are WordPress.com and WordPress.org Related?” href=”http://www.wpbeginner.com/beginners-guide/how-are-wordpress-com-and-wordpress-org-related/”>the relations and differences</a>)

Furthermore, the wording through out the process does not make it clear that you’re authorizing WordPress.com rather than your actual site. See the confirmation screenshot below:

<img class=”alignnone size-full wp-image-25084″ title=”Connected to Facebook” src=”http://cdn.wpbeginner.com/wp-content/uploads/2014/12/connected-to-fb.png” alt=”Connected to Facebook” width=”520″ height=”293″ />

Now if you want publicize to do what it’s suppose to (automatically share your post when its published), this is what your users will see.

<img class=”alignnone size-full wp-image-25089″ title=”A Post shared on Facebook using JetPack’s publicize module” src=”http://cdn2.wpbeginner.com/wp-content/uploads/2014/12/shared-post-fb1.png” alt=”A Post shared on Facebook using JetPack’s publicize module” width=”520″ height=”307″ />

We did some further research to find that it’s not a new problem. It has been<a title=”Support thread about Publicize” href=”http://en.forums.wordpress.com/topic/why-does-my-custom-publicize-message-say-published-an-article-on-facebook#post-1571896″ target=”_blank” rel=”nofollow”>reported</a> <a title=”Published an article on WordPres, why not my website name ?” href=”http://en.forums.wordpress.com/topic/published-an-article-on-wordpress-why-not-my-website-name” target=”_blank” rel=”nofollow”>several</a> <a title=”Vikas published an article on WordPress, but I published on waystoworld.com” href=”http://en.forums.wordpress.com/topic/vikas-published-an-article-on-wordpress-but-i-published-on-waystoworldcom” target=”_blank” rel=”nofollow”>times</a> since 2013.

Considering Jetpack is auto-installed and auto-activated on several major<a title=”WordPress Hosting Providers” href=”http://www.wpbeginner.com/wordpress-hosting/”>WordPress hosting providers</a> by default, this should be corrected to decrease the confusion between <a title=”Self Hosted WordPress.org vs. Free WordPress.com – Infographic” href=”http://www.wpbeginner.com/beginners-guide/self-hosted-wordpress-org-vs-free-wordpress-com-infograph/” target=”_blank”>WordPress.com vs self-hosted WordPress.org</a>.

While we understand that Facebook has it’s limitation, there are certain things that can and should be corrected to better inform users.

<del datetime=”2015-01-05T16:31:36+00:00″>First, in the link data below post title, it should actually show the user’s domain to promote their brand instead of showing WordPress.</del> As Jeremy from the Jetpack team pointed out in the comments below, this is not possible due to Facebook restrictions.

Second, the wording that says Syed Balkhi published an article on WordPress should be rephrased to clear confusion.

One of the user who reported the issue, offered a suggestion on wording: Vikas shared a link via Publicize instead of saying Vikas published an article on WordPress.

Another alternative could be: … shared a link via JetPack because that’s what is really going on.

Lastly, in the confirmation dialog, it should say “you have successfully connected Jetpack with Facebook” or “you have successfully connected your Facebook account with Jetpack”. [Update: <a title=”Jetpack Github ticket” href=”https://github.com/Automattic/jetpack/pull/1476″ target=”_blank” rel=”nofollow”>Ticket #1476</a> created by Jeremy]

We hope these suggestions help improve the Jetpack Publicize experience for users.

<a title=”JetPack for WordPress” href=”http://jetpack.me/” target=”_blank” rel=”nofollow”><img class=”alignnone size-full wp-image-25174″ title=”Jetpack Image” src=”http://cdn.wpbeginner.com/wp-content/uploads/2015/01/jetpack1.jpg” alt=”Jetpack Image” width=”520″ height=”252″ /></a>

Jetpack is a great plugin for beginners who <a title=”How to Properly Move Your Blog from WordPress.com to WordPress.org” href=”http://www.wpbeginner.com/wp-tutorials/how-to-properly-move-your-blog-from-wordpress-com-to-wordpress-org/”>move from WordPress.com to WordPress.org</a> because it allows you to retain a lot of cool features of WordPress.com while giving you the power and freedom of WordPress.org.

Note: The goal of this post is not to start a flame war rather it is to encourage discussion and share our opinion with the community. We have tremendous respect and appreciation for Automattic and the work they’ve done.

If you liked this article, then please subscribe to our <a title=”WPBeginner on YouTube” href=”http://youtube.com/wpbeginner” target=”_blank” rel=”nofollow”>YouTube Channel</a> for WordPress video tutorials. You can also find us on <a title=”WPBeginner on Twitter” href=”http://twitter.com/wpbeginner” target=”_blank” rel=”nofollow”>Twitter</a> and <a title=”WPBginner on Google+” href=”https://plus.google.com/101634180904808003404/posts” target=”_blank” rel=”nofollow”>Google+</a>.

from :http://www.wpbeginner.com/opinion/is-jetpack-misusing-your-brand-to-promote-wordpress-com/

[quote font=”verdana” font_size=”14″ font_style=”italic” color=”#474747″ bgcolor=”#F5F5F5″ bcolor=”#dd9933″ arrow=”yes” align=”centre”]This Demo Content Brought to you by <a href=”http://momizat.com/” target=”_blank” rel=”dofollow”>Momizat Team</a> [/quote]
<h2>this is tags and keywords : wordpress themes momizat Tutorial wordpress  templates</h2>