18

Another possible reason for the Object DOMDocument should be created. error is the unaccessible ui_component/your_listing.xml file under the view/adminhtml/ folder when you want to create an Adminhtml Grid and you declare it under the view/adminhtml/layout/your_handle_index.xml as this: <body> <referenceContainer name="content"> <...


13

I found the "steps to reproduce" and hotfix. Originally we enabled the "Website Payments Standard" payment method and then disabled because we had the problem with "Suspect Fraud" status. Immediately after I disabled the "Website Payments Standard" it turned into "Website Payments Standard (Includes Express Checkout)" and I was not able to revert it back. ...


12

I still don't know how to reuse the knockout Ui form components on front-end, but sharing code just in case someone needs to use jquery-ui calendar. Add an input to your front-end form: <input type="text" class="input-text required-entry" id="calendar_inputField" name="calendar_inputField" aria-required="true" > and write this js code after the ...


10

Another possible reason for this error is if your class folders don't have proper capitalization (i.e. are lowercase). var/log/system.log: [2016-02-26 21:19:51] main.CRITICAL: Class Example\Myclass\Block\ShopCategory does not exist [] [] [2016-02-26 21:19:51] main.CRITICAL: Invalid block type: Example\Myclass\Block\ShopCategory [] [] For example, if the ...


8

What kind of patch or official statement do you expect? The blog post only says that a web application can be compromised once the attacker has access to the code. That applies to each and every web application. The term Magento is completely interchangeable there. Currently, they do not have a clue how the affected host was compromised. The open door in the ...


8

Looks like var/generation is not writable. Make sure to set proper file system ownership and permissions: var, app/etc and pub/static should be writable by web server.


6

So the most problematic index in terms of performance is catalog_url. I have had a similar experience on some larger shops (although not as large as 1M products). The major problem was that the number of records in the core_url_rewrite table was much larger than (#products + #categories) x #stores. I have found two causes for this, and found a solution/...


6

The Magento UI Library has a lot of useful UI components organized into reusable 'widgets'. These are things like calendar, modal (popup), tabs, etc. You initialize the widget on your element, and then the JS widget takes care of it from there. There are a number of ways to instantiate widgets. The best way is to do it in HTML via a data-mage-init attribute....


4

First, extend your API call to pass the limit parameter. $client = new SoapClient('http://magentohost/api/soap/?wsdl'); $session = $client->login('apiUser', 'apiKey'); $limit = 5; $result = $client->call($session, 'your_extension.getCustomers', $limit); var_dump($result); Let's assume the getCustomers() method you posted above is the method which ...


4

you don't need to edit any of the cron files, it's not even recommended. catalog rules do have some problems, but they can be solved directly or by adding an extra cronjob. the reason you're not seeing the cronjob in the db is because the job runs daily at 1:00 AM GMT and gets cleaned up after a few hours. You can use n98-magerun to list your cron jobs, ...


4

There's the API references in the official documentation: http://devdocs.magento.com/guides/m1x/ Regarding code reference, I'm not aware of any official resource unfortunately.


4

There is actually a Magento 1.x Reference, but it's not quite the same as the one from WordPress. The Magento 1.x reference is mostly about installations, upgrades, patches, and customizations: http://devdocs.magento.com/guides/m1x/. I remember there was also once a documentation of classes and methods online. The most similar thing I could find right now ...


3

As long as your Magento version is up to date, you've installed all latest patches and your server meets best practice regarding setup (file permissions, not another software/website running, firewall, etc.) this is all you can do for now. I think it's important to mention that there is no specific attack vector yet: So how does attack work? We’re still ...


3

No, this is not native functionality.


3

Looking at your code, the first thing that pops out is you're using a PHP short tag to start your PHP file `<?` You'll want to change that to `<?php` My guess if your server is setup with the short_open_tag ini set to false, which means <? will be interpreted as a regular bit of text.


3

I did something similar for multiple configurable products in a lightbox. First thing you need is your block to show the products configurable html. You'll probably extend this from Mage_Catalog_Block_Product_List. In this block, create a method /** * Gets the configurable options template if needed * * @param Mage_Catalog_Model_Product $product * @...


3

Be sure you are not adding the same attribute twice with addAttributeToSort in any of your collections. As you already mentioned be sure none of your layout's are including the catalog/layer_view block types. <catalog_category_layered> <reference name="left"> <block type="mymodule/catalog_layer_view" name="mymodule.navleft" ...


3

I have Magento EE 2.2.4 as well Community edition 2.2.4 I have did some r&d for this and I have not found any Magento DevDocs Information regarding this, But I have some idea because I am working in EE and below information might be helpful for you. I have summon information from multiple source as well with my inputs and my local database for cross ...


2

You only have to create the 0.4.9 - 0.5.0 script. Magento will automatically pickup the skip in version numbers.


2

Most likely some files got missing during failed update. A reasonable way to recover is to download a vanilla Magento to your pc, extract the archive and copy app/code/core to your server with ftp/rsyn/sftp


2

Ok, I debugged my cron.php 2 days ago, and I found out that the var $isShellDisabled was set to false. So it executed this block of code: else if (!$isShellDisabled){ $fileName = basename(__FILE__); $baseDir = dirname(__FILE__); shell_exec("/bin/sh $baseDir/cron.sh $fileName -mdefault 1 > /dev/null 2>&1 &"); shell_exec("/bin/...


2

Below free giftcard extension you can use http://www.magentocommerce.com/magento-connect/devsters-gift-cards.html Also you try below links https://github.com/WarbyParker/Warby_BulkGiftAccount https://github.com/merchantwarehouse/shopping-cart-integrations/tree/master/magento


2

Because unsetChild isn't working in this case, I suggest the nuclear option: <checkout_cart_index> <remove name="checkout.cart.coupon"></remove> </checkout_cart_index> This will remove the block entirely. Not such a big deal because you'll immediately re-create it: <checkout_cart_index> <remove name="checkout.cart....


2

Magento Upgrade Procedure for 1.9 to 1.9.1. Generally all Magento upgrades work by running the updated code with the old database. The differences will be detected and incorporated automatically on the next page request. Magento keeps track of every module's version number for this reason. This is not advised with this upgrade if you have custom code. ...


2

I feel that you might be missing some files when you FTPed everything over. I would suggest migrating over to a version control system so you can verify all the files are correctly in place. To many things can go wrong by not using a version control system.


2

Something about this old question just jumped out to me - in your screenshot you have created a Block which extends the Mage_Core_Block_Template class. However, your block methods are named as actions, indicating that this may be controller code. Further, you're using loadLayout and renderLayout - both are methods that come from the ...


2

Enterprise has 41 modules that are separate from the community edition code base. These include modules which cover areas such as: Search Indexing Catalog Page Caching Reward Points So while the core magento Mage_* functionality should be expected to be the same, depending on what functionality you are looking to make use of it may very well be that the ...


2

The easiest way of getting email address in customer edit section (admin side) is shown below. $customer = Mage::registry('current_customer'); $emailAddress = $customer->getEmail(); Magento will register the customer whose details are editing via admin in the controller action itself (refer : Mage_Adminhtml_CustomerController::editAction()) and hence ...


2

It seems you already answered your own question. I've placed the RewriteCond line and the RewriteRule line from your question in my .htaccess file (after the already existing 'RewriteEngine on') and did a curl request from my terminal to see what happens; ➜ hackathon curl -vvv http://hackathon.dev/customer/account/index\?___store\=tienda * Trying 127.0....


2

Not (only) Magento I've seen many other websites hacked this way, inserting malicious code into the code base, and not only in Magento. And there are many variants: scripts stealing POST data, scripts adding XSS, scripts trying to steal root passwords, scripts allowing incoming calls to process data (for Bitcoin mining, to send spam emails from that server),...


Only top voted, non community-wiki answers of a minimum length are eligible