Our project which was migrated from typo3 version 9 to version 10. The issue is storagepid = 0. I can hardcode the pid value to configuration. But that’s not a permanent solution. If I use same plugin in different project again I have to hardcode storagepid value. So I need a permanent solution to fix it out.Can anyone help me to find out the solution?
There is no need to hardcode the storagePid in PHP code, since TYPO3 Extbase plugins typically will fetch the storagePid(s) from configuration (either TypoScript, starting point or plugin settings).
This blogpost I wrote some years ago explains, how and in which order Extbase will determine the storagePid.
The most suitable way is to use the starting point setting in the plugin, which automatically will be taken into account when data is fetched (e.g. in a Extbase repository). This way, you can use the plugin in several projects and the editor can select the storagePid(s) directly in plugin settings.
Related
I have to make an update from Typo3 8 to Typo3 9.5 LTS. And i have some trouble with the Flux extension which causes some strange errors. I have used Flux 9.4.2 (latest) and Typo3 LTS (9.5.22). I have used Composer for the new version perhaps that causes the problem.
I have followed all the steps in this tutorial and some others instructions but all of them ends in the same error.
https://sigalambigha.home.blog/2020/04/29/how-to-migrate-fluidcontent-to-flux/
In Backend i get the following error:
And in the Frontend i get this error:
This depends on the Flux element which is on that page the Slider element. The Plug & Play configuration is disabled because of some other errors. Perhaps now i missed something in my configuration but i can't find something in the documentation to configure.
Edit
I have made some more tests an i think the problem is that the newest version of Flux is not really compatible with Typo3 9.5. So i changed to version 9.3.2 which is working better but has other bugs.
Make sure these 3 things in your template provider extension are set correct:
Register the provider extension key using the Vendor.ExtName syntax, not ext_name. Here is an example:
\FluidTYPO3\Flux\Core::registerProviderExtensionKey('Nng.MyExtname', 'Page');
\FluidTYPO3\Flux\Core::registerProviderExtensionKey('Nng.MyExtname', 'Content');
Place the above code in the ext_localconf.php of your extension, not the ext_tables.php. You can find this hint hidden in the documentation.
In older versions of FLUX you might also need to create a ClassAliasMap in EXT:myextensionkey/Migrations/Code/ClassAliasMap.php. Here is a simple example.
Did you try to set a small condition for the used parameter if it's null? that maybe can give an error message instead of the error in the page.
Or you should see if there's any error in the namespace
After upgrading Flux to Typo3 9.5 then you have to register "VendorName" with your content element using Typoscript like i did below.
tt_content {
mytemplate_wrapelement.20.vendorName = <vendorname>
}
here mytemplate is my template provider extension.
Wrapelement is the content element.
I was getting same error.
I upgraded typo3 version 8 to 9.
There are some extension that can not update for version9
extensions: cookieconsent2, crawler, realurl
These extension do not exits for version-9 but installed in version-8, what is solution for that.
how i can use it or what is alternate for typo3 version-9
Thanks AbdulQayyum.
crawler is about to get ready for v9 https://github.com/AOEpeople/crawler/projects/3. If you do not have a complicated setup, you can just have your frontend crawled by something else, e.g. wget -r https://your-site.com as a workaround in the meantime. You probably want EXT:indexed_search to work. This automatically updates the search index when cacheable pages are visited.
realurl is not needed in v9. SEO-routes are now part of the core. You need a site configuration (this is a write-up how it looks like: https://typo3worx.eu/2018/10/typo3-site-management-and-routing/) and that's all.
cookieconsent2 you may ask the developers if it will get updated. If not, there are alternatives: https://extensions.typo3.org/?L=0&id=1&tx_solr%5Bq%5D=cookie+consent
I am trying to migrate a website from Typo3 4.0 to a fresh new server with Typo3 8.7. I have exported the tree structure from the root page on the old CMS, selecting all levels and tables. When I try to import it on the new CMS I get the following error:
The reference UID for the file (sys_file_reference) has to be numeric
I found this bug report, which states that the bug has been updated for version 6.2. How can I avoid having sys_file_reference records with relations to sys_files records during the export? Or is there another way to fix this error?
With 6.0 the file handling of TYPO3 has changed drastically: FAL was introduced.
As of this change you cannot transfer data from an older version to a newer one. you need to do an update in place.
The neccessary way would be:
make a clone of your 4.0 installation
update to 4.5 (this should be easy as till then not much was deprecated)
update to 6.2 (in this upgrade all file references are transformed into FAL)
update to 8.7 [1]
For Step 3 and 4 you may need to update extensions and their data to a matching version.
[1] you wrote about 8.3. this was an intermediate version which is not support in any way.
Always use the latest version, which is 8.7 (for the 8 version) in the latest (current) subversion 8.7.8
I've migrated from typo3 4.1 to 4.5 LTS now I got this error.
The page is not configured! [type= 0][]
I've checked DB analyser and fixed the table issues any ideas. Please revert
Apparently TYPO3 can't find TypoScript use Web > Template tool and check if record exists, also if it includes TS from external files, make sure the files exists.
Is there any working Forum extension for TYPO3 6.2.
I have tried mm_forum with some patches, but id does not work.
I have also looked at extension repository but without any luck.
Any help is welcome :)
The new forum extension from Mittwald is typo3_forum (6.2 und 7.x)
Link in Typo3-Repo: http://typo3.org/extensions/repository/view/typo3_forum
How to migrate your mm_forum to typo3_forum:
Install typo3_forum
Execute the Scheduler Task Database Migration
Open your root TypoScript Template Record and include typo3_forum's static TypoScript
Change your TypoScript configuration (e.g. in your template extension or Typoscript records) from plugin.tx_mmforum to plugin.tx_typo3forum
Uninstall mm_forum
Clean up the database using the Install Tool "compare" functionality.
If you have custom fluid templates for the forum using the forum's ViewHelpers you have to adjust the namespace declaration accordingly. E.g. {namespace t3f=Mittwald\Typo3Forum\ViewHelpers}
You could check the multiblog-extension, it´s up to date and ready for TYPO3.CMS 6.2.