typo3 create double root page - typo3

I'm new to typo3 and I just came across through a backend of a certain website and found two issues. Why there are two duplicated root pages within the same website as shown on the picture attached? How can I create something like this?typo3 backend

This could be an issue with the db_mountpoints in your usergroups.
Have a look at the database table "be_users" and the field "db_mountpoints". If there is a usergroup which has the value "0" it will lead to the problem you have.
If a usergroup should not have a db_mountpoint the value must be "null" not "0".

Related

Get value from Pages data type in page types in Kentico

I have a Pages data type as one of the page type fields.
But when I try to access it's value using the Macro like {% JoinPageLink %}, I don't get any values (empty).
I can access rest of the fields in that page type.
Appreciate any help.
The Pages type creates an ad-hoc relationship name for the page type. Its value in the page type table in the database is always NULL, so when you try to access it using {%JoinPageLink%}, you won't get a value. Kentico describes this as Advanced Content Modeling.
To make use of the Pages type, you will need to use something like a transformation to retrieve your data. There is a page on DevNet that gives detail on using a listing control to display the relationship information: Displaying related pages using web parts

How can I store flux form fields defined in TYPO3 page templates in database columns instead of flex fields?

Using flux to create custom content elements for TYPO3, fields that are defined in a flux:form are stored in a flex field as XML by default. By the solution Claus Due pointed out here (Fluidtypo3 Flux - save in table field), they can also be stored as individual columns in tt_content.
Now, when creating page templates and defining template parameters as flux input fields, could those be stored as indiviual columns in the "pages" table?
The obvious approach to do this in the same way as described for content elements, i.e.:
<flux:field.text name="pages.extrafield" label="Content" />
did not work. (I created the field "extrafield" in the pages table using my extension's ext_tables.sql)
The format you used is the correct one, but in order to get the field saved it first must be 1) allowed for the user who saves and 2) shown somewhere in the form; types passthrough and none should also work.
The last requirement is a safeguard added in a recent major version and is there to prevent doing things that normally would be prohibited by access settings or field availability.

List all "incoming" internal links / references to a TYPO3 element

I need to get a list of elements linking to a specific TYPO3 page or element (all IDs oder pages, that link or refer to a this element). I thought this was at the Info module, but I can't find it.
I have spent hours finding this info on the web and even in my oldschool TYPO3 manual book... nothing, but I know that I once had this list.
Thanks a lot in advance! (version is TYPO3 4.6, I am preparing an upgrade right now)
You could search your database manually to find such links. I will start to give you a list where you could search for.
Find tt_content headers which link to a page, element or any url:
SELECT * FROM tt_content WHERE header_link NOT LIKE '' AND deleted = 0;
In RTE fields, you could manually check.
Go to backend modul 'Configuration', choose '$TCA (Tabel configuration array)' and search for 'RTE'.
Then you schould get all RTE fields, which could have links set to any TYPO3 pages or elements.
Like fx: tt_content.bodytext.config.wizards.RTE...
These fields you could search for any links vis MySQL
SELECT * FROM tt_content WHERE bodytext LIKE '%<link%' OR bodytext LIKE '%<LINK%' AND deleted = 0;
Maybe someone can add more default fields not listed above.
I think you have seen the references of a record normaly seen in the list module.
If you hover your mouse over the count you get a list of origins.
That list is not always up to date and the usability of the origins differs from version to version. Sometimes you can use the origins as direct link to edit the origin record.
Maybe you had an extension which enhances the usage.
In gerneral: if records are used with TYPO3 (TCA group fields which build relations to other records with uid-lists, or mm-records) this is also stored as refrence.
As links are also relations they are not always stored as referenes, espeacially if the link is inside a textfield.

laravel 5.2 user login redirect with condition

I am making Dating website using laravel 5.2
I have Tables in database
--user
--profile
--education
--Occupation
--Marital Status
--Parents Details
Each of the table has user_id as forigen key of User table.
All models have been created and hasMany and belongsTo relation has been added respectively.
My question is when user login, I would like user to land to specific create controller if table is unfilled or form is not filled. For EX- profile.create, education.create , occupation.create.
Or is there any efficient way I can handle this situation.
Thanks in advance, I hope you got it. Let me know if you still need any more info.
The most simple idea below:
Create a column full_profile (tinyint, length 1) in your table which indicates the profile is full. Default it's 0.
After a validations are true, set the value of the full_profile to 1.
Ok, now it's simple:
User logs in
Check the value of full_profile. If 0, redirect to form, if 1, redirect to dashboard?

Google Chart - DataTable inside a form

I have a table created with DataTable of Google Chart, which has a column with a drop-down list. In this way the user can set the proper value of a row.
I am working in Python and Flask and I can retrieve the request data correctly. The problem is that the table, given the amount of data, is showed in pages, each one with 20 rows. When I retrieve the request I get only those 20 rows, so I have no way to know what the user set in the other pages.
How can I get the values of all pages?
Moreover, I noticed that when I change page and then I go back, the table forgets the user changes, so I think I should be careful also to this fact.
Finally, I solved the problem by using a dictionary containing all the changes made to the table and updating the html string inside the table to keep the content updated.