AllVideos (by JoomlaWorks) is truely THE all-in-one media management solution for Joomla!. You can use the plugin to easily embed videos hosted on popular services like YouTube, Metacafe, Vimeo (and many more) inside your Joomla! articles (content items).

Additionally, it allows you to playback almost any video/audio filetype directly from your server or a remote server, giving you the competitive edge when it comes to rich media content.

Extension Name: AllVideos

Extension Provider: JoomlaWorks

Price: Free

More info and reviews: AllVideos on JED


To download this extension Click Here

In this article, we are going to discuss about How to run multiple websites from a single CodeIgniter (CI) install. CodeIgniter is a powerful PHP framework with a very small footprint, built for PHP coders who need a simple and elegant toolkit to create full-featured web applications. If you're a developer who lives in the real world of shared hosting accounts and clients with deadlines, and if you're tired of ponderously large and thoroughly undocumented frameworks

Each CodeIgniter website have a different "application" folder. But all are using the same "System" folder.

Take the application folder out from the system folder and make an additional copies based on the number of sites your need to create. For example, if you want to create 3 sites then, create the application folder names like "application_site1, application_site2, application_site3".

Now copy the index.php file to the root of each website folder, and edit it as follows:

At line 26, put the full path to the system folder:

$system_folder = dirname(__FILE__) . '../codeigniter/system';

At line 43, put the full path to the application folder:

$application_folder = dirname(__FILE__) . '../application_site1';

Now you can have independent websites using separate application folders, but sharing the same system folder.

There is a similar implementation in the CodeIgniter User Guide you can read also.

In this article, we are going to discuss about How to add Icon for new products in Magento. As your inventory rises it's always very necessary to make your products stand out using an unique icon. Visitors to your website will be able to notice which products are newly arrived as the icon will show up in wherever you set it to in your theme.

Step 1: Manage attributes

Go to Catalogue -> Attributes -> Manage Attributes. Set up a new attribute at this page and call it 'Boolean'. Set its ID as new_product. Under your advanced options, you will have the option to select it as a front end product. Do this. Now you simply have to add the new attribute to your custom attribute if you are using one. If not, set it to default. Save the new product.

You will now have a new product in your catalogue which has a Boolean flag set to yes. The next stage involves taking this new product icon and putting it in your front end.

Step 2: Make it show

Now that you have a product icon with a Boolean flag, it's time to make this show on your front end. This is achieved by accessing template files: templates/catalog/product/list.phtml and templates/catalog/product/view/media.phtml.

<div class="product-image">
<?php if($_product->getNewProduct()) { ?>
<div class="new-product"></div>
<?php } ?>
<?php
$_img = '<img id="image" src="'.$this->helper('catalog/image')
->init($_product, 'image').'" 
alt="'.$this->htmlEscape($this->getImageLabel()).'" 
title="'.$this->htmlEscape($this->getImageLabel()).'" />';
echo $_helper->productAttribute($_product, $_img, 'image');
?>
</div>

As you can see, above, your new product is shows in '$_product->getNewProduct'. The next step is to ensure that your CSS is set up to show your product with Boolean flag. You need to make the product_class relative to the position of the icon. So:

.products-grid .product-image { position: relative; display:block; width:244px; height:156px; margin:0 0 10px; }
.new-product {position: absolute;right: 0;top: 0;width: 65px;height: 66px;display: block;z-index: 2;background: url(../images/new-product.png) no-repeat;}

Step 3: Save

Save your changes and ensure that your code is correct before doing so. Now, every time you add a new product and it goes on sale through your front end, it'll have an icon and Boolean flag.

In this article, we are going to discuss about How to install DebugKit in CakePHP on ubuntu 14.04. CakePHP is an open source web application framework. It follows the Model-View-Controller (MVC) approach and is written in PHP, modeled after the concepts of Ruby on Rails, and distributed under the MIT License.

CakePHP uses well-known software engineering concepts and software design patterns, as Convention over configuration, Model-View-Controller, Active Record, Association Data Mapping, and Front Controller.

Requirements to install DebugKit:

1. CakePHP 2.2.0 or greater.
2. PHP 5.3.0 or greater.

Follow the below steps to install DebugKit in CakePHP on Ubuntu.

Step 1: 

Open terminal and first of all install git if not installed already.

$ sudo apt-get install git

Step 2: 

Go to app/Plugin folder where DebugKit will be installed.

$ cd /var/www/html/cake/app/Plugin

Now initialize git repository here so that we can clone the DebugKit through GitHub using git.

$ sudo git init

Step 3:  

To clone DebugKit type this command:

$ sudo git submodule add https://github.com/cakephp/debug_kit.git

or use this command:

$ sudo git clone https://github.com/cakephp/debug_kit.git

When this process is done then a folder will be created named as debug_kit in Plugin folder. Rename this folder as DebugKit. Type following command to do this:

$ sudo mv debug_kit/ DebugKit

[Note: Make sure you are in the Plugin folder.]

Step 4: 

Go to app/Config folder

$ cd /var/www/html/cake/app/Config
$ sudo nano bootstrap.php

Add this line in the file CakePlugin::load('DebugKit'); if not already present.

Press ctrl+x, press y and enter to save file. Refresh localhost/cake page. Now DebugKit is detected.

Step 5: 

After this check whether this line is present in core.php file or not Configure::write('debug',2); If it's not present then add this line and save file. Core.php file is present in app/Config. To edit this file type this:

$ sudo nano core.php

Step 6: 

Now add DebugKit toolbar. Go to app/Controller folder.

$ cd app/Controller
$ sudo nano AppController.php

Add the red text color line in the empty class AppController which is present at the end of the file.

class AppController extends Controller {
         public $components = array('DebugKit.Toolbar');
}

Press ctrl+x, press y and enter to save file. Refresh localhost/cake page. DebugKit toolbar is added at the top right end of the page.

Step 7: 

After this go to app/View/Layouts folder to remove sql_dump.

$ cd app/View/Layouts
$ sudo nano default.ctp

Comment the following line present at the end of file embedded in php tags i.e. in between these tags <?php ?>

<?php //echo $this->element('sql_dump'); ?>

Press ctrl+x, press y and enter to save file. Refresh localhost/cake page.

Installation is DONE!!! Hope you get the points and this post is helpful for you. If you have any query then comment on the post. i'll get back to you as soon as possible. All The Best.

In this article, we are going o discuss about how to add HTTp authentication to the Drupal website. HTTP authentication is quite useful to be added on your live site when you need only the authenticated people to have the access.

Step 1 :

Create the file that will keep the information of the usernames / passwords for authentication. (You can create more than one accounts). You can create this file in the project root folder. Like, the location /var/www/drupal_site/. Use the following command.

htpasswd [ -c ] passwdfilename username 

So, here you have given the username that would be authenticated for the site. You will be asked twice to enter password for this username.

For example, in the following command, my file's name is ".dummyhtpasswd" and the username of the account is "user1".

htpasswd –c /var/www/drupal_site/.dummyhtpasswd user1

Step 2:

You are done with creation of account details, now you need to edit your .htaccess file to add the code for http authentication there and also to add the path of this newly created file that contains the credentials' information so that this newly created file's presence and the credentials are verified at every http access. For that you have to reach out to your .htaccess file. In my case, I found it in my project folder at /var/www/drupal_site/ . You can also find it in the folder of your project.

Step 3:

Now, edit the .htaccess file. By using the below command.

vi .htaccess

Now to go to edit mode, press "i", that's for "insert". Take the cursor to the very bottom of the code and then add the following lines.

# /var/www/drupal_site/.dummyhtpasswd
# AUTHENTICATION
## BASIC PASSWORD AUTHENTICATION
AuthName "Prompt"
AuthUserFile /var/www/drupal_site/.dummyhtpasswd
AuthType basic
Require valid-user

That is it. Now we have to save it. Press "Esc" and then :w <enter>. This saves it.

For saving and exiting press "Esc" and then press :wq! <enter>.

Now we have added the path of the newly created file. Please see that line 1 and 5 of the code would have the path of "your" created file, in above code I have given the path of "my" created file for reference.

Step 4:  

You have to reach out to the newly created file. (You created in Step 1). After that the following command can be used to add a user to the already existing file.

htpasswd /var/www/ drupal_site/.dummyhtpasswd  newuser <enter>

Enter the password twice and you are done. The path in above command will be the path for that newly created password file (of Step 1).

Done!!

In this article we are going to discuss about How to restrict access to wordpress files using htaccess file. It will restrict a number of files on your website from being accessed from an external source.

Htacess to restrict access to a single WordPress file

In the .htaccess file example below, we are restricting access to the WordPress wp-config.php file.

<files wp-config.php>
 order allow,deny
 deny from all
</files>

The .htaccess file in the above example should be uploaded to the same directory where the file resides, in this case in the WordPress root directory. If you would like to restrict access to any other individual file on your website change the file name in the first line and upload the .htaccess file to the directory where the file resides. Keep in mind that if you already have an .htaccess file in that directory, simply add the above directives at the end of the .htaccess file.

Restrict file access to by file type with htaccess

To restrict access to a variety of files which share the same file extension, you can use the syntax of the .htaccess file below. Such .htaccess file should be uploaded to the root of your website to apply file restriction site wide. In the below example, we are restricting access to .htaccess files, .htpasswd files, log files and ini files.

<FilesMatch "\.(htaccess|htpasswd|log|ini)$">
 Order Allow,Deny
 Deny from all
</FilesMatch>

If you would like to restrict access to more file extensions than the ones specified above, add the extension to the first line between the brackets next to the ini extension.

In this article, we are going to discuss about the two controller methods in YII, render and renderPartial. Both the render and renderPartial methods are used to creating the controller's view content. Simply put this is the information the view will receive from the controller.

The difference between render and renderPartial is that the latter will not load the layout. This is useful in case you'd like to have a popup window or ajax functionality which shows short information.

Here is an example with a whole method:

public function actionView($slug) { 
    $model = $this->loadSlug($slug);
    $category = $this->loadCategory($model->category); 
    $this->render('view', array( 'model' => $model, 'category' => $category->category )); 
}

The first argument for render is view. This is the view file to which will be added .php. This should be the file protected/views/view_name/view.php.

The next interesting thing is the array which comes as second argument. This is how you set the properties or variables that will be sent to the view and will be available there. In our case we will have $model (array) and $category at our disposal in the view file.

Eventually you could create variables in the view and you don't have to necessarily pass them from the controller. However, this will not be in the spirit of MVC.

In this article, we are going to discuss about How to create custom Toolbar for ZendDeveloperTools using Zend Framework 2. ZendDeveloperTools toolbars are great to help us debug our application. However, when we need to have additional toolbar that not yet in it, we need to add it by creating custom toolbar for it. Ok, for example, we want to add a session toolbar that read our current session Container key -> value like this :


To make it easy to learn, let's apply it into new module, I created a new module for it named SanSessionToolbar like the following :


1. Start with the Collector :

namespace SanSessionToolbar\Collector;

use ZendDeveloperTools\Collector\CollectorInterface;
use Zend\Mvc\MvcEvent;
use Zend\Session\Container;

/**
 * Session Data Collector.
 */
class SessionCollector implements CollectorInterface
{
    /**
     * @inheritdoc
     */
    public function getName()
    {
         // this name must same with *collectors* name in the configuration
        return 'session.toolbar';
    }

    /**
     * {@inheritDoc}
     */
    public function getPriority()
    {
        return 10;
    }

    /**
     * @inheritdoc
     */
    public function collect(MvcEvent $mvcEvent)
    {
    }
   
    public function getSessionData()
    {
        $container = new Container;
        $arraysession = $container->getManager()->getStorage()->toArray();
       
        $data = array();
        foreach($arraysession as $key => $row) {
            if ($row instanceof \Zend\Stdlib\ArrayObject) {
                $iterator = $row->getIterator();
                while($iterator->valid()) {
                    $data[$iterator->key()] =  $iterator->current() ;
                    $iterator->next();
                }
            }
        }
       
        return $data;
    }
}

2. Now, create a view to var_dump the
SanSessionToolbar\Collector\SessionCollector::getSessionData().

<?php /* @var $collector \SanSessionToolbar\Collector\SessionCollector */ ?>
<div class="zdt-toolbar-entry">
    <div class="zdt-toolbar-preview">
        <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAYAAACNiR0NAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAATxJREFUeNpi/P//PwMhMJuRkRVItQNxKhBzAPFOIM5O/f//MbpaFgbiAMigYiS+LxCDXOKPrpCJSAP1sYiZY1NIrIGHsYhtw6aQWC8vA2IlIM4EYn6oYRXYFDISEylokQOKlG/ACPlLsguBBggAKRUglgbi70B8EWjQS3x6sLoQaFAikLIDYjcglkKSegHEGUBDN+IyEFekeAOxJRBfAeJPSOISQDwZaKEYSS5Ec20KiEITVgW68g65yeYHAwmAGAN90PgPgPgjWQZCw8oOTXgX0LuvyXWhBxBLIvFBaW8zJV52RePfA+LdZBkI9K44kHJAEz4G9O5Pcl3IA8QyaGJHKYllRixiylDXywCxFKkGvgPiG2hiJUCDQHn5PhBbkGQgMKxABsYC8UEg/grFH4D4BBDHA/EebPoAAgwA3RZUHjvT8+IAAAAASUVORK5CYII=" alt="SESSION Data">
        <span class="zdt-toolbar-info">
                SessionData    
        </span>
    </div>
    <div class="zdt-toolbar-detail">
        <span class="zdt-toolbar-info zdt-toolbar-info-redundant">
            <span class="zdt-detail-label">Session Data</span>
        </span>
        <span class="zdt-toolbar-info">
            <span class="zdt-detail-pre">
                <?php Zend\Debug\Debug::dump($collector->getSessionData()); ?>
            </span>
        </span>
    </div>
</div>

3. Configure the module configuration ( config/module.config.php ), Remember, that the toolbar entries name must same with our SessionCollector::getName().

return array(
   
    'service_manager' => array(
        'invokables' => array(
            'session.toolbar' =>
                'SanSessionToolbar\Collector\SessionCollector',
        ),
    ),
   
    'view_manager' => array(
        'template_map' => array(
            'zend-developer-tools/toolbar/session-data'
                => __DIR__ . '/../view/zend-developer-tools/toolbar/session-data.phtml',
        ),
    ),
       
    'zenddevelopertools' => array(
        'profiler' => array(
            'collectors' => array(
                'session.toolbar' => 'session.toolbar',
            ),
        ),
        'toolbar' => array(
            'entries' => array(
                'session.toolbar' => 'zend-developer-tools/toolbar/session-data',
            ),
        ),
    ),
   
);

The 'session.toolbar' must be registered into ServiceManager with an instance of SanSessionToolbar\Collector\SessionCollector, and registered into 'zenddevelopertools' config profiler and toolbar.

4. The Module.php is a usual Module class.

5. Register your new module into config/application.config.php

6. Now, let's test it by creating session data in our controller :

public function indexAction()
{
    $container = new \Zend\Session\Container;
    $container->a   = 'b';
    $container->foo = 'bar';
   
    return new ViewModel();
}

Source :

https://samsonasik.wordpress.com/2014/06/27/zend-framework-2-create-custom-toolbar-for-zenddevelopertools/

Reference :

1. http://stackoverflow.com/questions/20325842/how-to-log-something-to-zend-developer-tools-toolbar
2. Image session icon originally from : http://makemore.info.yorku.ca/files/2012/11/info.png, encoded with base64_encode.