How can i set up multisite in typo 3 version 11.5.8?
The extensions available on the internet are for versions upto 10.
I get the error shown in the diagram below, when I try to install multisite extension from typo3 GUI
Sure, you need this extension?
TYPO3 is out-of-the-box a multisite-system:
https://typo3.org/cms/features/massively-multisite-multilingual
EXT:multisite
That extension may solve special requirements for huge multisites. What a "huge multisite" looks like in numbers is written in its doc:
We have a multisite installation with
600 website (root pages)
3.500 frontend users 400 frontend user groups
60.000 pages
250.000 content elements
3.000 categories
100.000 news
5.000 news categories
So, for this (or a similar) use-case, the backend can get slower. EXT:multisite changes some behaviors of the backend to speed up operations.
For a "normal" TYPO3 instance with a couple of sites/rootpages and fewer pages/records, the basics of TYPO3-Core will met all requirements for a multisite.
Related
I have just started working on TYPO3 10 and I'm looking to make 3 websites with different domain URLs.
In TYPO3 9, I usually define the domains using the "domain record" in the list module, but in TYPO3 10 I can't find it. It seems that the domain record is no longer available in TYPO3 10.
My issue is that each site is under the same domain with a predefined identifier, I would like to have a different domain for each website.
Can somebody explain how the multidomain works in TYPO3 10?
Since TYPO3 9, the domain handling has changed quite a lot. The new way to create multi-language and/or multi-domain setups is using site configurations. There's a new backend module called "Sites" where you can configure your domains and languages.
If you want to manage three different websites with three different domains, create three different site configurations in the "Sites" module.
You can find detailed informations in the official TYPO3 docs.
This concerns the typo3 v9 main page tree in the backend view.
I have a very large page tree with about 20.000 page entities. The query takes a long time...
In my Typo3 v9.5.5 environment, the data is retrieved in a single slow query.
How can Typo3 build the page tree in several fast queries level by level?
In the older Typo3 version (8.7.24) this also works with the method getNextTreeLevel() I think.
The core team is working on it.
There are 2 patches pending:
https://review.typo3.org/c/Packages/TYPO3.CMS/+/62329 - this patch makes page tree less bandwidth
https://review.typo3.org/c/Packages/TYPO3.CMS/+/62086 - this adds asynchronous tree rendering (it's a work in progress, as needs some tuning regarding workspaces support)
The new behaviour is like this by design in TYPO3 9.
There is a slack-channel discussing that issue: https://typo3.slack.com/messages/CK20S7EKS
And a bug-ticket on forge: https://forge.typo3.org/issues/88474
Out of that there will come a patch for the core.
The only help for now is the extensions: https://github.com/bueroparallel/bp_pagetree (discussed and reviewed in the slack channel). This speed up the tree load but just loads up to a defined nesting level what results in not all pages are automatic included in the filter results. But for now (and hopefully just for a small time period) the best solution!
We are migrating a TYPO3 4.7.14 site with news 1.4.0 to TYPO3 7.6.28 with news 6.3.0.
When we started all news are migrated and are ok on the new server.
But in the time after the news migration some news are added to the old site and now they must be migrated to the new server.
How could this be done?
A t3d Export / Import don't work.
The news are containing a lot of content elements, so it would be an incredible amount of work to do it by hand.
I'd advise to make the whole migration-process new, perhaps only with the news-pages, news-plugins (content-elements saved in the table tt_content with the list_type tx_news or resembling) and news-records.
Problem is primary the update to version 6.2 of TYPO3 as the FAL (file abstraction layer) was introduced and all media-files in the news are getting lost if the corresponding update is not done properly.
Keep in mind that you've to care about one setting in file-storage records (usually for the fileadmin-folder): the checkbox that case-sensitive filenames are allowed. Else a mess is predictable and much additional work too.
If you do it like I proposed only for the news-records and related records, you've to export and import also the tables starting with sys_file, but keep in mind that you really import only then in the upper version instead overwriting the whole table, as there might be still other media-files.
For the construction of an extensive list of links, since the source page is a thematic portal, I am looking for a suitable EXT., Which also runs under TYPO3 7.6 LTS.
it if the list of links to a permits the use of categories and multiple categorization of links is possible would be nice. should Weiterrhin the links are described not only the destination address and an alias but here should still an outline of the target page (possibly with photo) be possible.
Additional functions such as proposing links by users, reporting broken links or even a User Voting would nice additional features.
There were times the Modern Linklist, but they were no longer being developed for TYPO3 <6.x.
Is there perhaps somewhere an alternative or as one might like to vorhnandenen solutions might realize? It would be nice of course, without any programming knowledge, since I'm not a programmer.
P.S .: It is not about building a spam list but high quality links with topics relating to the original page.
As this seems to be a straight forward usage you could try to build that extension by yourself with the ExtensionBuilder.
just build up the records neccessary for your data. and let the EB generate all usefull actions: list & show, even create, edit, delete in FE would be possible.
Afterwards you just need to edit the generated fluid templates.
these links may help:
Overview
EB manual
small remark: if you want the newest code state, use the EB from git instead of TER
I`m not aware of an existing extension for it but it could be a good project to learn extbase / fluid.
You should also take a look at
typo3/sysext/fluid_styled_content/Resources/Private/Partials/Menu
and
typo3/sysext/fluid_styled_content/Classes/ViewHelpers/Menu
Fluid Content contains everything you need to create a list like that, you "just" have to combine the necessary bits and pieces.
You can do a lot with TYPO3 core functionality: there is a page type "external URL", pages can have categories by default, there are plenty of menu options (TypoScript HMENU, menu content elements, Fluid menu Viewhelpers). The Linkvalidator can periodically check all links and report broken links.
For suggestions you could add a form. Powermail for example can also store submitted info in database records, so your visitors could prepare page records (they are hidden until you make them visible).
I am new to TYPO3. A customer wants TYPO3. It's a quite large project with WIKI, JOBS, NEWS, PROJECTS, etc.
As far as I can see, there are several ways I could go.
What would you as an experienced TYPO3 developer suggest as the easeast, fastest, most efficient approach to reach our goal?
A: Leave the object graph in TYPO3
A1: I've seen with the DOMAIN_MODEL classes there is some kind of rudimentary ORM integrated. This approach means, we would need to reevent the wheel with WIKI, NEWS, etc.
A2: It would be great to use existing extentions for WIKI, NEWS,... The customer wants them to be related (add a wiki entry to news or new to projects). That means the existing extentions have to be extented
B: Use TYPO3 only for normal content like pages (legal, contact, landig pages...) and as a backend for dynamic content as well, which is stored and handled in an external API. This approach also means, we would need to reevent the wheel with WIKI, NEWS, etc.
I would suggest to use TYPO3 for content and news (use news extension for that) and look for a suitable standalone wiki solution. Then connect both systems the way you need them to interact. No wheels have to be reinvented.