StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>A few things to try (obviously disable caching/APC/compilation/minification of JS,CSS/etc.):</p> <p><strong>Logs & Developer Mode</strong></p> <p>First I would enable developer mode via .htaccess SetEnv or simply uncommenting the flag in <code>index.php</code>. Also ensure that logging is enabled via the Admin. System->Configuration->Developer->Log Settings. Also check <code>var/logs/</code> for any existing exception.log or system.log with possible information to issues. It also doesn't hurt to check Apache and PHP's logs.</p> <p><strong>Paypal and Magento debugging</strong></p> <p>Something to note is since obviously Ebay has/had backing of Magento the Module is pretty highly customized, especially on the configuration, as you can tell. Some key files to step through with something like XDebug would be:</p> <p><code>app/code/core/Mage/Paypal/Model/Config.php</code> and the <code>..Paypal/Model/System/Config/*</code> directories and files, as these are what are driving some of the custom configuration options of the module. etc/system.xml is also an entry point to review as well for the modules configurations.</p> <p><strong>Reverting to Stock</strong></p> <p><strong>1)</strong> Copy from a fresh version of the Paypal module from a Magento 1.7.x source archive (ensure its the same version you are running!) </p> <p>copy the <code>app/code/core/Mage/Paypal</code> from the source archive</p> <p>to <code>app/code/local/Mage/Paypal</code></p> <p>(NOTE: PaypalUk module may also be good to copy down to local as well)</p> <p>This should be a quick and easy way to check if there any missing files, damaged/corrupted, and/or core file that was modified.</p> <p><strong>2)</strong> Revert all theme/skins to the <code>base/default</code> theme. A quick way to do this is System->Design->Add Design Change.</p> <p><strong>3)</strong> Make a backup of <code>core_config_data</code> and remove all instances of the <code>path</code> that contains paypal, payment and payflow. </p> <p><code>SELECT * FROM core_config_data WHERE path LIKE '%paypal%' OR path LIKE '%payflow%' OR path LIKE '%payment%';</code></p> <p>This should revert any configuration changes previously done back to the defaults specified in the modules xml.</p> <p>The point of most of these steps is to get the payment module back to as much stock as possible.</p> <p>Hope this helps!</p> <hr> <p>Sonassi has a good detailed fundamentals as well for debugging magento worth a read:</p> <ul> <li><a href="https://magento.stackexchange.com/questions/428/fundamentals-for-debugging-a-magento-store/429#429">https://magento.stackexchange.com/questions/428/fundamentals-for-debugging-a-magento-store/429#429</a></li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload