Closed GoogleCodeExporter closed 8 years ago
I wouldn't bother with this.
Let's just provide a clear explanation and forget about it.
You sort of explained the background, but still need to give detailed
instructions.
Original comment by ad...@zetaprints.com
on 22 Mar 2012 at 7:32
I think you did
Instructions to make w2p work after compilation.
After compilation process finished, please do following:
1. Edit includes/src/ZetaPrints_Api.php file.
Replace
require_once 'zetaprints-api.php';
with
require_once 'ZetaPrints/zetaprints-api.php';
2. Copy XSLT files (compilation process doesn't move them automatically)
Copy lib/ZetaPrints/xslt to includes/src/ZetaPrints
Original comment by ad...@zetaprints.com
on 22 Mar 2012 at 7:33
I can't say that I understand this thing so I'm just gonna copy the previous
comment as a help post.
Original comment by agur...@gmail.com
on 22 Mar 2012 at 9:14
What you didn't understand?
Original comment by Anatoly....@gmail.com
on 22 Mar 2012 at 9:42
I understand that hack it self, as in how to implement. Just need to read a bit
so that I can offer an introduction on what magento compiler actually is and
what it does.
Original comment by agur...@gmail.com
on 22 Mar 2012 at 9:47
From http://alanstorm.com/magento_compiler_path (be careful with the quote and
link to the source)
Magento’s source is spread out over a large number of modules.
It turns out that having PHP search for a large number of include files over a
large number of different directories can create a performance bottleneck under
certain types of load. To combat this, the Magento core team created the
Magento Compiler extension, and started shipping Magento with this
functionality around version 1.4 CE.
What the compiler does is makes a copy of every class in a Magento system and
places them in a single folder. The class’s full name is used for the
filename to ensure uniqueness
include/src/Mage_Core_Model_Abstract.php
include/src/Foo_Module_FooController.php
etc...
This is done once. Then, when Magento is configured to use the compiler
classes, its autoload will look in the compiler folder instead of running its
normal autoload routine. This spares PHP the overhead of transversing the file
system for all the different include paths.
Original comment by ad...@zetaprints.com
on 22 Mar 2012 at 10:07
check and publish:
http://www.zetaprints.com/magentohelp/web-to-print-extension-and-magento-compile
r/
Original comment by agur...@gmail.com
on 29 Mar 2012 at 1:23
Original comment by ad...@zetaprints.com
on 3 Apr 2012 at 12:29
Original issue reported on code.google.com by
Anatoly....@gmail.com
on 22 Mar 2012 at 3:57