I'm using TYPO3 V11.5 with an extension, which has only a backend module.
Therefore it doesn't exist any configPlugin and also no ext_localconfig and under Configuration->TCA->Overrides no tt_content.php file.
If I try to call the backend I get the following error message:
What is required to avoid this error or is it an TYPO3 bug?
Edit
Stupid misteake, forgot to include the extension template under Template->Includes!
Without having too much code I guess it is because the class really does not exist! Is the file really called BackEndController and also the class in it BackEndController with an uppercase E?
Related
I have upgraded TYPO3 version from 9 to 10. But my custom extensions throwing
(1/1) #1239891990 InvalidArgumentException
The extension name must not be empty
error while I am trying to re-activate those.
Thank you in advance
Please check your extension for the usage of one of these methods:
\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin()
\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerPlugin()
\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerModule()
Most probably you have to search in ext_localconf.php, ext_tables.phpor any file in Configuration/TCA/Overrides.
The first parameter of each of these methods is the extension name (in UpperCamelCase) or the extension key (in lower_underscore). This is missing according to your error message.
Maybe your extension relies on $_EXTKEY. Starting with TYPO3 10 LTS the variable $_EXTKEY isn't filled with the extension key anymore. Solution: use the hardcoded extension key within ext_tables.php and ext_localconf.php. See the documentation for details.
odoo/odoo/addons/base/models/ir_ui_view.py", line 592, in raise_view_error
raise ValueError(message)
ValueError: Field `invoice_is_snailmail` does not exist
Error context:
View `n/a`
[view_id: n/a, xml_id: n/a, model: n/a, parent_id: n/a]
I check in my code invoice_is_snailmail this files written in files but still odoo though an error
I am beginner in odoo developer. can you please answer.
The field invoice_is_snailmail is a field in standard Odoo module snailmail_account. If you want to use this field in your custom module, you need to install snailmail_account module first.
Best practice is to list the dependent module snailmail_account as a dependency in your module so that Odoo will install it automatically. More info on module definition and depends can be found here: https://www.odoo.com/documentation/13.0/reference/module.html, see manifest field depends.
If this does not help you, you need to provide more information in your question, e.g your source code for your custom module. Without your exact code it is hard to help more, see question guidelines at https://stackoverflow.com/help/how-to-ask.
Please Provide Code Screenshots or check fields define in py and xml in same module or field for xml in child module.
We are using TYPO3 8.7.19 with the extension frontend_editing (Version: 1.4.0) and CoolURI. We still use css_styled_content.
When editing a content element in the frontend with the „frontent-editing bar”, e.g. text I get an error, but only, if it contains an internal link.
The changes are not saved. It crash with:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1460629247: No valid handlers found for type: unknown | TYPO3\CMS\Core\LinkHandling\Exception\UnknownLinkHandlerException thrown in file /usr/share/typo3/typo3_src-8.7.19/typo3/sysext/core/Classes/LinkHandling/LinkService.php in line 163. Requested URL: https://www.mysite.de/typo3/index.php?ajaxID=%2Fajax%2Ffrontend-editing%2Fprocess&ajaxToken=--AnonymizedToken--&page=123
There is a bug report and a suggested solution für TYPO3 9.5.x and a solution for TYPO3 8.7.x
Unfortunately, I don't know how to realize that solution for my system, cause
wee use coolURI but not the required realurl-xtension.
I don't know where to add the suggested code
Any hints for me?
Problem has been solved by the author of frontend_editing:
Add in typo3conf/ext/frontend_editing/Configuration/TypoScript/setup.ts
# Prevent links from being parsed to FE url
lib.parseFunc_RTE.tags.a >
I'm using Typo3 6.2 and I want move my Projekt to another Computer with Typo3 6.2 but I'm failing to import the tree structure ...
When I'm import a single page it works but when if the page has a subpages it doesnt work.
After I uploading a receive this Error:
"Possible error: pages:15 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!"
Here is the import file, maybe it just doesnt work on my system...
File leist.t3d
means
I had this error, too.
In my case, I got an error message after enabling error messages, it was a missing field in table "pages", after a "DB compare", the import worked.
Not sure, but is sounds like a known bug:
https://forge.typo3.org/issues/59055
Or more specific (copy pasted from that bug):
When I change uniqid('NEW'); to uniqid('NEW', TRUE); in class
ImportExport the functional tests aren't failing and I assume
introduction extension is imported correctly (no errors in typo3.log).
(again not totally certain) but you might wanna patch it for testing or fetching a patched source for
/typo3/sysext/impexp/Classes/ImportExport.php
I've disabled the Rss and Newsletter modules of my Magento 1.7 instance following the instructions of this post:
http://inchoo.net/ecommerce/magento/how-to-fully-disable-turn-off-magento-module/comment-page-1/#comment-65853
I just edited the app\etc\modules\Mage_All.xml file by changing to <active>false</active> in both Mage_Rss and Mage_Newsletter modules.
The problem is that when I try to load a customer page through admin panel, I get the following error:
Fatal error: Call to a member function loadByCustomer() on a
non-object in app\code\core\Mage\Newsletter\Model\Subscriber.php on
line 267
Why is it happening? Why is this code being executing even though I've disabled such module?
Thanks!
First step after disabling a module through its <active> entry. Always clear cache and if you use the compiler, recompile so you don't have code referencing classes in the disabled module.
Often the problem is not with code executing after the module is shut off through the app/etc/modules/mod_name.xml by setting <active> to false, but with other modules, templates or layouts attempting to call code in the disabled module.
Where issues come in are if another module lists the module just turned off in its dependency list. Always check all the other module xml files dependency lists for mention of the module you are deactivating.
Also, you have to check for template .phtml files that reference classes in the disabled module. This can throw the dreaded call to a non-object type exception errors. As an example, one module that provides custom cart attributes asks you to add entries to your cart templates. Shutting off the module does not get rid of the references.
Make sure no layouts are attempting to load anything referencing this module as well (custom layout local.xml).
You also might want to go to System Config, Advanced and shut the Newsletter module output off there in case the Magento Customer Account is depending on testing for the module being disabled by calling that entry instead of actually checking to see if the Module is loaded. Sometimes Magento programmers forget to do proper error trapping, which has thrown me for a loop before.
I believe I could solve the problem (not sure if generated any side effect):
Just edited the file app\code\core\Mage\Adminhtml\Block\Customer\Edit\Tabs.php around line 90 by adding the external if clause:
if (Mage::helper('core')->isModuleEnabled('Mage_Newsletter')) {
if (Mage::getSingleton('admin/session')->isAllowed('newsletter/subscriber')) {
$this->addTab('newsletter', array(
'label' => Mage::helper('customer')->__('Newsletter'),
'content' => $this->getLayout()->createBlock('adminhtml/customer_edit_tab_newsletter')->initForm()->toHtml()
));
}
}
+1 if I saved your day and please let me know if you noticed and possible impact :D