Fatal error: Class 'Raveinfosys_Exporter_Helper_Data' not found in ..\app\Mage.php on line 546.
I have installed new new extension Bulk Import+Export Orders to CSV in Magento 1.7, but I am getting above fatal error in admin. Any help is appreciated.
I struggled with this error in this extension for quite some time when I figured out the solution (for me, at least). Disable compilation in System > Tools > Compilation. Once you disable compilation, install the extension, clear the Magento cache (I left the cache page opened in another tab to make sure I had access to it) and you should see an "Exporter" tab in the header. Hope this solves your issue because it took me many hours to find the problem.
Related
I am using php-cs-fixer for code formatting in Netbeans 8.2. When I try to format one file, it shows the error
Files that were not fixed due to errors reported during linting after fixing:
I searched for the fix in many websites, but couldn't get this fixed. Is there any way to fix this? I tried with both php-cs-fixer 1 and php-cs-fixer 2.
The error message means that PHP CS Fixer loaded some files from drive, apply changes on them, and then realised that files are not valid anymore (invalid PHP syntax) after those changes, thus it decided to not save it. That's one of the safety mechanism of PHP CS Fixer to not break your project.
This means that you have found an issue in PHP CS Fixer itself.
Please, verify you are using newest release, maybe the bug was already fixed!
If not, please consider to expose your configuration file (if any) and content of files you got listed at https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/new !
There is also an option to see what happen in progress.
$ ./vendor/bin/php-cs-fixer fix src/ErrorFile.php -vvv
The --verbose option will show the applied rules. When using the txt format it will also display progress notifications.
NOTE: if there is an error like "errors reported during linting after fixing", you can use this to be even more verbose for debugging purpose
-v: verbose
-vv: very verbose
-vvv: debug
I'm new to Netbeans Platform Development and following this tutorial.
When I try to build the project I get this error:
Module org.netbeans.modules.editor.util excluded from the target platform
There are apparently no errors in the app.
I'm using
NB 8.0
JDK jdk1.7.0_45
OS Win 8.1
What might be going wrong?
UPDATE:
Somehow the module was excluded via the disabled.modules in the platform.properties properties file.
When i comment it out (or remove it), it runs but gives this warning
Regards,
I nailed part of the problem. The error occurred because of unresolved dependencies.
I went through the tut again on a Linux Mint with NB7.4.
Now I get no errors but facing yet another problem. Now as I open a file, it opens the file but the Cookie Editor disappears.
I'm expecting someone will help on the second Issue.
Moderators: I'm not sure how will you guys respond to this but I've no clue how to go about my half solved problem.
On installing mageworx seo suite ultimate extension in magento
"Fatal error: Call to a member function setLayer() on a non-object in \app\code\core\Mage\Catalog\Block\Layer\View.php on line 134"
is displayed.
Even after deleting all the files that I had uploaded this error is displayed.
Try to completely delete the extension. Follow the instructions given here: http://support.mageworx.com/index.php?/Knowledgebase/Article/View/74/4/how-to-remove-the-seo-suite-ultimate-magento-extension
Then install the module again. This is likely to solve the issue.
However, if the issue persists, please contact our support team: http://support.mageworx.com/
In conjunction with the failed installation of an extension (yag), the install tool is no longer available with the following error message:
PHP Fatal error: Class '\\tx_install_session' not found in /var/typo3_src-6.0.2/typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 4158
Any suggestions are welcome.
Ok, I'm one step further.
Assuming the backend login works, it helps to clear the cache via the flash button.
Which leads me to the question: Is there a way to do this in the shell in case the BE login is broken?
Remove/comment the bad extension in the LocalConfiguration.php file and then remove content of /typo3temp/Cache/ directory.
It will allow you restore to the state before the malformed installation.
I've updated my Typo3 from 4.5.5 to 4.7.0 and I get several deprecated errors:
ERROR: Content Element type "login" has no rendering definition!
call to undefined error in t3lib_div::view_array
fail to include class.t3lib_htmlmail.php
The install tool gives me "typo3/ext/ directory not writable" but I've the correct right. I've even allow all?????
When I select a CType Element in the BE it give me this warning: PHP Warning
PHP Warning: Invalid argument supplied for foreach() in /var/www/typo3_src-4.7.0/t3lib/l10n/parser/class.t3lib_l10n_parser_llphp.php line 95
The solution for 2. is to use the new class t3lib_utility_debug but what is with the other errors?
Edit: 1. http://lists.typo3.org/pipermail/typo3-english/2011-November/078129.html
Edit 2: The solution for the missing class t3lib_htmlmail is to include another class t3lib_mail_message: require_once(PATH_t3lib .'mail/class.t3lib_mail_message.php');
You solved allready: install system extension "felogin"
you solved allready: use t3lib_utility_debug
check where the error is from. Often it is helpfull to search for that file in typo3conf/temp_*.
You could check your filesystem, if your webserver is allowed to write to typo3/ext/. I guess, it is not. But you do not need to. Usually you install extensions to typo3conf/ext/.
Update your language files via the extension manager.
Well, i know it is to late now, but for all others wo think about an update: just activate the deprecation log in the isntall toll and fix that problems first!
Updating from 4.5.X to 4.7.x broke my felogin as well. The reason was that there has been a local extension installation that has been of higher priority than the system one. So if you suffer the same update issue, check for an local installation of felogin in "typo3conf/ext" - and delete it in case it is there. This solved my problem!