The post Disabled module will be enabled by bin/magento setup:upgrade appeared first on My Silly Point of View.

$proxy = new SoapClient('http://your.magento.domain/api/v2_soap/?wsdl');
$sessionId = $proxy->login('username', 'password!');
$product = new stdclass();
$product->attributes = array(
     'description',
     'short_description',
     'price',
     'custom_attribute_code'
);
$data = $proxy->catalogProductInfo($sessionId, $sku, null, $product);
var_dump($data);

The above var_dump() would show the values of requested fields except the custom_attribute_code. The reason for this is because a custom product attribute is available in additional_attributes property instead.

Get custom product attribute:

To get the value of custom_attribute_code, use the following code:

$proxy = new SoapClient('http://your.magento.domain/api/v2_soap/?wsdl');
$sessionId = $proxy->login('username', 'password!');
$product = new stdClass();
$product->additional_attributes = array('custom_attribute_code');
$data = $proxy->catalogProductInfo($sessionId, $sku, null, $product);

The post How to pull custom product attribute using SOAP API in Magento appeared first on My Silly Point of View.

Solution:

To do that, you must open the file js/mage/adminhtml/wysiwyg/tiny_mce/setup.js and locate the line below:

var settings = {

Right after the code plugins : plugins, add the lines highlighted in grey:

        var settings = {
            mode : (mode != undefined ? mode : 'none'),
            elements : this.id,
            theme : 'advanced',
            plugins : plugins,
            forced_root_block: false,
            extended_valid_elements: '+ul[*],+li[*],+p[*],+span[*],+div[*],+a[*]',
            remove_linebreaks : false,
            theme_advanced_buttons1 : magentoPlugins ...

Save the file and clear your cache to apply the changes.

The post Keep line breaks, custom HTML attributes and remove initial paragraph tag in Magento Admin’s TinyMCE editor appeared first on My Silly Point of View.

catalogProductCreate Error:

SQLSTATE23000: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (`db`.`catalog_product_super_link`, CONSTRAINT `FK_CAT_PRD_SPR_LNK_PRD_ID_CAT_PRD_ENTT_ENTT_ID` FOREIGN KEY (`product_id`) REFERENCES `catalog_product_entity` (`entity_id`) ON DELETE CASCADE)

An empty url_key value causes the above issue. To fix it, make sure that the configurable product being created has a valid url_key. This is required for any product that is available on both catalog and search listings as shown below:

Do not forget that a url_key needs to be unique because this is used to generate the hyperlink of the product.

The post catalogProductCreate in Magento API returning SQL error for configurable product appeared first on My Silly Point of View.

Upon investigation, I noticed that the method _beforeSave() is being called multiple times regardless if the field is for timezone or not as shown in the screenshot below:

The error occurs when the value of a non-timezone field is validated against the array result of the method DateTimeZone::listIdentifiers($allWithBc).

To fix this, duplicate the core file:

app/code/core/Mage/Adminhtml/Model/System/Config/Backend/Locale/Timezone.php

into this path (create the directory if it doesn’t exists)

app/code/local/Mage/Adminhtml/Model/System/Config/Backend/Locale/Timezone.php

Locate the method _beforeSave() and add the code below at the beginning:

if($this->getField() !== 'timezone')
    return $this;

The content of the method _beforeSave() should be similar to the one below (note this is for Magento CE 1.7.0.2 so adjust accordingly with the code changes)

protected function _beforeSave()
{
    if($this->getField() !== 'timezone')
        return $this;

    $allWithBc = self::ALL_WITH_BC;
    if (defined('DateTimeZone::ALL_WITH_BC')) {
        $allWithBc = DateTimeZone::ALL_WITH_BC;
    }

    if (!in_array($this->getValue(), DateTimeZone::listIdentifiers($allWithBc))) {
        Mage::throwException(Mage::helper('adminhtml')->__('Invalid timezone'));
    }

    return $this;
}

After that, you should now be able to save your configuration changes in the admin.

The post How to fix the Invalid Timezone error in Magento appeared first on My Silly Point of View.

Parse error: parse error in /app/design/frontend/base/default/template/fontis/australia/ payment/directdeposit/form.phtml on line 42

Some would ask you to check the file permission while others would tell that you need to turn off compilation. If you did all these already and still see the error, I would suggest for you to check if short_open_tag is enabled in your php.ini file. This setting enables the syntax <? ... ?> to work instead of typing <?php … ?>.

Upon checking the form.phtml file, the code in line 31 would show that it is using the short_open_tag (see code below) so you must change it from:

<?endif;?>

to this:

<?php endif;?>

Refresh your page to see the now working Direct Deposit block.

The post Fixing Fontis’ Parse Error when using Direct Deposit appeared first on My Silly Point of View.

Open the catalog.xml file which can be found in the location below:
/app/design/frontend/<package-name>/<theme>/layout/catalog.xml

Locate the line that declares the block for product listing similar to the one below:
<block type="catalog/product_list" name="product_list" template="catalog/product/list.phtml">

Immediately after the code above, add the XML node below:
<action method="setColumnCount"><columns>4</columns></action>

Save the file and clear the contents of your var/cache directory. Reload the catalog page to see the changes

Note: You can also apply this to catalogsearch.xml or any layout XML file that uses the list.phtml

The post How to change the number of columns in Magento catalog grid appeared first on My Silly Point of View.

Not Found
The requested URL /~user/wordpress/category/sample/ was not found on this server.
Apache/2.2.21 (Unix) DAV/2 PHP/5.3.10 with Suhosin-Patch Server at localhost Port 80

To fix this, create a file and name it <username>.conf, where username is your user account’s short name. Paste the text below within the file:

<Directory "/Users/username/Sites/">
Options Indexes MultiViews FollowSymLinks
AllowOverride All AuthConfig
Order allow,deny
Allow from all
</Directory>

Save the file and make sure it uses the .conf extension. Copy the file to this location (you may need to provide your credentials to overwrite the current one):

/etc/apache2/users/

Restart Apache to apply the changes by running the following in the Terminal:

sudo apachectl restart

Reapply your permalinks in the WordPress admin by choosing the default option and then setting it back to your desired format.

The post How to fix WordPress permalinks on Mac OS X’s localhost appeared first on My Silly Point of View.

Everything went well during the installation except when I access the frontend (http://localhost/magento) and admin (http://localhost/magento/admin), I was greeted with the default error page like the one below:

The page itself is not helpful so I decided to check the content of the error log (htdocs\magento\var\report) record number 1742231029 which contains the following information:

a:5:{i:0;s:67:"Illegal scheme supplied, only alphanumeric characters are permitted";i:1;s:681:"#0 C:\xampp\htdocs\magento\app\code\core\Mage\Core\Model\Store.php(712): Zend_Uri::factory('{{base_url}}')
#1 C:\xampp\htdocs\magento\app\code\core\Mage\Core\Controller\Varien\Front.php(313): Mage_Core_Model_Store->isCurrentlySecure()
#2 C:\xampp\htdocs\magento\app\code\core\Mage\Core\Controller\Varien\Front.php(161): Mage_Core_Controller_Varien_Front->_checkBaseUrl(Object(Mage_Core_Controller_Request_Http))
#3 C:\xampp\htdocs\magento\app\code\core\Mage\Core\Model\App.php(349): Mage_Core_Controller_Varien_Front->dispatch()
#4 C:\xampp\htdocs\magento\app\Mage.php(640): Mage_Core_Model_App->run(Array)
#5 C:\xampp\htdocs\magento\index.php(80): Mage::run('', 'store')
#6 {main}";s:3:"url";s:19:"/magento/index.php/";s:11:"script_name";s:18:"/magento/index.php";s:4:"skin";s:7:"default";}

As you can see, the cause of the error is the invalid config data format being passed during the start of a session. To fix this, we need to accomplish these tasks:

1. Allow the admin panel to run on localhost by disabling the domain check.
2. Fix the config data value.

Allow the admin panel to run on localhost.

You will need to follow the instructions in my previous post but instead of using HTTP, you must access the admin page via HTTPS after you applied the code changes.

Fixing the config data value.

Once you are able to access the admin panel using HTTPS, go to System > Configuration > General > Web. Make sure that you supply the proper value for the Base URL on both Unsecure and Secure tabs then save the changes. See my example below:

Clear your browser’s cache and also Magento’s cache by deleting all the contents (not the folder itself) of the cache directory (htdocs\magento\var\cache). At this point, you should be able to access the frontend and admin panel using HTTP protocol.

The post How to fix the “Illegal scheme supplied, only alphanumeric characters are permitted” Magento error on Localhost using HTTP (fresh install) appeared first on My Silly Point of View.

Let’s start with creating the markup of the form. Save the HTML below and name it as index.htm (we won’t be needing PHP stuff for now in this exercise.)

<!doctype html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>Sample Form</title>
<script type="text/javascript" src="//ajax.googleapis.com/ajax/libs/jquery/1.5.2/jquery.min.js"></script>
</head>

<body>
	<form id="myForm" action="index.html" method="post" onSubmit="return false;">
		<select id="do-not-select" name="do-not-select[]" multiple="multiple" size="3">
			<option>Do</option>
			<option>not</option>
			<option>select</option>
		</select>
		<select id="color" name="color[]" multiple="multiple" size="3">
			<option>Red</option>
			<option>Green</option>
			<option>Blue</option>
		</select>
		<select id="size" name="size[]" multiple="multiple" size="3">
			<option>Small</option>
			<option>Medium</option>
			<option>Large</option>
		</select>
		<select id="category" name="category[]" multiple="multiple" size="3">
			<option>Children</option>
			<option>Ladies</option>
			<option>Men</option>
		</select>
		<input type="submit" value="Submit" />
	</form>
</body>
</html>

The markup above will create a single form with an id of myForm having four (4) multi-select field with the following ids:

• do-not-select
• color
• size
• category

At line 6, we added the jQuery file (latest version 1.5.2 as of this writing) to use it’s functionality in manipulating DOM objects. Now for the real action, copy the code below and insert it between line 6 and 7:

<script>
$(document).ready(function() {
	$('#myForm').submit(function() {
		$('#color, #size, #category').find('option').each(function() {
			$(this).attr('selected', 'selected');
		});
	});
});
</script>

The script above will do the following task:

1. Instruct the browser to execute the script within $(document).ready(...); when the page has loaded.
2. Trigger the script within $('#myForm').submit(...) once the form with an id of myForm is submitted.
3. With the given SELECT element ids (color, size, category), find all OPTION tags in each of them and add the attribute and value selected="selected"

We also added at line 10 the event handler onSubmit with return false; to prevent the page on submitting while we are testing the script.

That’s it! Load the file on your browser and click Submit button. It should highlight all the options under color, size and category while ignoring the do-not-select option since we didn’t add them in the affected elements. See the full markup below. Remember to remove the onSubmit="return false;" in the FORM tag to enable redirection of your form on submit.

<!doctype html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>Sample Form</title>
<script type="text/javascript" src="//ajax.googleapis.com/ajax/libs/jquery/1.5.2/jquery.min.js"></script>
<script>
$(document).ready(function() {
	$('#myForm').submit(function() {
		$('#color, #size, #category').find('option').each(function() {
			$(this).attr('selected', 'selected');
		});
	});
});
</script>
</head>

<body>
	<form id="myForm" action="index.html" method="post" onSubmit="return false;">
		<select id="do-not-select" name="do-not-select[]" multiple="multiple" size="3">
			<option>Do</option>
			<option>not</option>
			<option>select</option>
		</select>
		<select id="color" name="color[]" multiple="multiple" size="3">
			<option>Red</option>
			<option>Green</option>
			<option>Blue</option>
		</select>
		<select id="size" name="size[]" multiple="multiple" size="3">
			<option>Small</option>
			<option>Medium</option>
			<option>Large</option>
		</select>
		<select id="category" name="category[]" multiple="multiple" size="3">
			<option>Children</option>
			<option>Ladies</option>
			<option>Men</option>
		</select>
		<input type="submit" value="Submit" />
	</form>
</body>
</html>

The post Auto-select all <option> items from multiple select dropdown using jQuery appeared first on My Silly Point of View.

First, include the file Mage.php from your Magento installation to your PHP file. Doing this will enable you to connect to your shop using the Mage object.

If you’re using Mage Enabler for WordPress, you may skip this part:

<?php
require_once ("/your/magento/app/Mage.php");
umask(0);

and here’s the rest of the code…

// Customer Information
$firstname = "John";
$lastname = "Smith";
$email = "johnsmith@localhost.local";
$password = "myverysecretpassword";

// Website and Store details
$websiteId = Mage::app()->getWebsite()->getId();
$store = Mage::app()->getStore();

$customer = Mage::getModel("customer/customer");
$customer->website_id = $websiteId;
$customer->setStore($store);

try {
	// If new, save customer information
	$customer->firstname = $firstname;
	$customer->lastname = $lastname;
	$customer->email = $email;
	$customer->password_hash = md5($password);
	if($customer->save()){
		echo $customer->firstname." ".$customer->lastname." information is saved!";
	}else{
		echo "An error occured while saving customer";
	}
}catch(Exception $e){
	// If customer already exists, initiate login
	if(preg_match('/Customer email already exists/', $e)){
		$customer->loadByEmail($email);

		$session = Mage::getSingleton('customer/session');
		$session->login($email, $password);

		echo $session->isLoggedIn() ? $session->getCustomer()->getName().' is online!' : 'not logged in';
	}
}

The above code tries to create a Magento customer account using the given parameters such as $firstname, $lastname, $email and $password. If the email doesn’t have a match in the database, the request proceeds. But if a match is found, it logs in the customer using the parameters $email and $password then checks if the customer is online or not logged in. There are actually more parameters that you can pass such as if you want to send confirmation message or not but these are the basic fields to help you get started.

I hope this will help you integrate the Magento registration to your external site

The post How to create a new Magento customer account from an external site? appeared first on My Silly Point of View.