Field missing in database upon .t3d Import

Questions around the TYPO3 integration and plugins as well as Flow and NeosCMS
Forum rules
Always add your TYPO3/Flow, Aimeos and PHP version as well as your environment (Linux/Mac/Win)
superscotty19
Posts: 90
Joined: 13 May 2019, 08:09

Field missing in database upon .t3d Import

Post by superscotty19 » 13 May 2019, 09:05

Hi,

TYPO3 8.7
Aimeos 19.4.1
Aimeos-pages_two-columns_18.10.t3d taken from https://github.com/aimeos/aimeos-typo3

Trying to follow the very simple/clear instructions of the "Page Setup", and I get slammed every time I try to import the .t3d file:

Specific steps taken:

In Web::Page, root page (the one with the globe)
Right click on the globe
Move the cursor to "Branch actions"
In the sub-menu, click on "Import from .t3d"
In the page import dialog
Select the "Upload" tab (2nd one)
Click on the "Select" dialog
Choose the file you've downloaded
Press the "Upload files" button

Result:

Nearly every record reports "Field missing in database" (see attached). Also, Messages tab looks like this:

Possible error: pages:114 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: pages:115 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: pages:116 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: pages:117 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: pages:118 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: pages:119 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: pages:120 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: pages:121 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: pages:122 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: pages:123 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: pages:124 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: pages:125 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: pages:126 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: pages:127 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: pages:128 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: sys_template:10 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: sys_template:9 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: sys_template:8 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: sys_template:7 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:268 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:267 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:266 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:265 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:264 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:263 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:262 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:261 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:260 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:259 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:258 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:257 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:256 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:255 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:254 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:253 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:252 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:251 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:250 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:249 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:248 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:247 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:246 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:245 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:244 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:243 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: tt_content:242 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: fe_groups:3 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Possible error: fe_users:5 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Error: this records is NOT created it seems! (pages:114)
Error: this records is NOT created it seems! (pages:115)
Error: this records is NOT created it seems! (pages:116)
Error: this records is NOT created it seems! (pages:117)
Error: this records is NOT created it seems! (pages:118)
Error: this records is NOT created it seems! (pages:119)
Error: this records is NOT created it seems! (pages:120)
Error: this records is NOT created it seems! (pages:121)
Error: this records is NOT created it seems! (pages:122)
Error: this records is NOT created it seems! (pages:123)
Error: this records is NOT created it seems! (pages:124)
Error: this records is NOT created it seems! (pages:125)
Error: this records is NOT created it seems! (pages:126)
Error: this records is NOT created it seems! (pages:127)
Error: this records is NOT created it seems! (pages:128)
Error: this records is NOT created it seems! (sys_template:10)
Error: this records is NOT created it seems! (sys_template:9)
Error: this records is NOT created it seems! (sys_template:8)
Error: this records is NOT created it seems! (sys_template:7)
Error: this records is NOT created it seems! (tt_content:268)
Error: this records is NOT created it seems! (tt_content:267)
Error: this records is NOT created it seems! (tt_content:266)
Error: this records is NOT created it seems! (tt_content:265)
Error: this records is NOT created it seems! (tt_content:264)
Error: this records is NOT created it seems! (tt_content:263)
Error: this records is NOT created it seems! (tt_content:262)
Error: this records is NOT created it seems! (tt_content:261)
Error: this records is NOT created it seems! (tt_content:260)
Error: this records is NOT created it seems! (tt_content:259)
Error: this records is NOT created it seems! (tt_content:258)
Error: this records is NOT created it seems! (tt_content:257)
Error: this records is NOT created it seems! (tt_content:256)
Error: this records is NOT created it seems! (tt_content:255)
Error: this records is NOT created it seems! (tt_content:254)
Error: this records is NOT created it seems! (tt_content:253)
Error: this records is NOT created it seems! (tt_content:252)
Error: this records is NOT created it seems! (tt_content:251)
Error: this records is NOT created it seems! (tt_content:250)
Error: this records is NOT created it seems! (tt_content:249)
Error: this records is NOT created it seems! (tt_content:248)
Error: this records is NOT created it seems! (tt_content:247)
Error: this records is NOT created it seems! (tt_content:246)
Error: this records is NOT created it seems! (tt_content:245)
Error: this records is NOT created it seems! (tt_content:244)
Error: this records is NOT created it seems! (tt_content:243)
Error: this records is NOT created it seems! (tt_content:242)
Error: this records is NOT created it seems! (fe_groups:3)
Error: this records is NOT created it seems! (fe_users:5)
Error: this records is NOT created it seems! (pages:114)
Error: this records is NOT created it seems! (pages:115)
Error: this records is NOT created it seems! (pages:116)
Error: this records is NOT created it seems! (pages:117)
Error: this records is NOT created it seems! (pages:118)
Error: this records is NOT created it seems! (pages:119)
Error: this records is NOT created it seems! (pages:120)
Error: this records is NOT created it seems! (pages:121)
Error: this records is NOT created it seems! (pages:122)
Error: this records is NOT created it seems! (pages:123)
Error: this records is NOT created it seems! (pages:124)
Error: this records is NOT created it seems! (pages:125)
Error: this records is NOT created it seems! (pages:126)
Error: this records is NOT created it seems! (pages:127)
Error: this records is NOT created it seems! (pages:128)
Error: this records is NOT created it seems! (sys_template:10)
Error: this records is NOT created it seems! (sys_template:9)
Error: this records is NOT created it seems! (sys_template:8)
Error: this records is NOT created it seems! (sys_template:7)
Error: this records is NOT created it seems! (tt_content:268)
Error: this records is NOT created it seems! (tt_content:267)
Error: this records is NOT created it seems! (tt_content:266)
Error: this records is NOT created it seems! (tt_content:265)
Error: this records is NOT created it seems! (tt_content:264)
Error: this records is NOT created it seems! (tt_content:263)
Error: this records is NOT created it seems! (tt_content:262)
Error: this records is NOT created it seems! (tt_content:261)
Error: this records is NOT created it seems! (tt_content:260)
Error: this records is NOT created it seems! (tt_content:259)
Error: this records is NOT created it seems! (tt_content:258)
Error: this records is NOT created it seems! (tt_content:257)
Error: this records is NOT created it seems! (tt_content:256)
Error: this records is NOT created it seems! (tt_content:255)
Error: this records is NOT created it seems! (tt_content:254)
Error: this records is NOT created it seems! (tt_content:253)
Error: this records is NOT created it seems! (tt_content:252)
Error: this records is NOT created it seems! (tt_content:251)
Error: this records is NOT created it seems! (tt_content:250)
Error: this records is NOT created it seems! (tt_content:249)
Error: this records is NOT created it seems! (tt_content:248)
Error: this records is NOT created it seems! (tt_content:247)
Error: this records is NOT created it seems! (tt_content:246)
Error: this records is NOT created it seems! (tt_content:245)
Error: this records is NOT created it seems! (tt_content:244)
Error: this records is NOT created it seems! (tt_content:243)
Error: this records is NOT created it seems! (tt_content:242)
Error: this records is NOT created it seems! (fe_groups:3)
Error: this records is NOT created it seems! (fe_users:5)

As a workaround, I just manually created the pages. However, I need the full TYPOscript templates for all the pages. So, could someone either help me fix the import or just provide the contents of each TYPOscript template per page?

Thanks!
-S.
Attachments
Screenshot_2019-05-13 STORM Lightning 8 7 4 [TYPO3 CMS 8 7 4].png
Screenshot_2019-05-13 STORM Lightning 8 7 4 [TYPO3 CMS 8 7 4].png (104.54 KiB) Viewed 415 times

User avatar
aimeos
Administrator
Posts: 3114
Joined: 01 Jan 1970, 00:00

Re: Field missing in database upon .t3d Import

Post by aimeos » 13 May 2019, 09:15

The link at the Github page pointed only to the page tree for Aimeos 18.10 LTS. This is fixed now and you should download the right version from there: https://aimeos.org/docs/TYPO3/Install_A ... s#Download
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, Image give us a star

superscotty19
Posts: 90
Joined: 13 May 2019, 08:09

Re: Field missing in database upon .t3d Import

Post by superscotty19 » 13 May 2019, 22:04

Thanks for the fast reply! ..... but that page https://aimeos.org/docs/TYPO3/Install_A ... s#Download also has a dead link,"for version 18.10+ and TYPO3 8.7, two column bootstrap_package page layout", which goes to a 404 Not Found page ( https://aimeos.org/fileadmin/download/A ... _18.10.t3d ). I need the page tree for 19.x on T3 8.7

User avatar
aimeos
Administrator
Posts: 3114
Joined: 01 Jan 1970, 00:00

Re: Field missing in database upon .t3d Import

Post by aimeos » 20 May 2019, 22:43

Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, Image give us a star

superscotty19
Posts: 90
Joined: 13 May 2019, 08:09

Re: Field missing in database upon .t3d Import

Post by superscotty19 » 22 May 2019, 07:15

Hi,

The link now works! I was able to download but this time when I import, the Meta Data tab says the following:

Code: Select all

Possible error: fe_groups:1 had no new id assigned to it. This indicates that the record was not added to database during import. Please check changelog!
Error: this records is NOT created it seems! (fe_groups:1)
Lost relation: fe_groups:1
Lost relation: fe_groups:1
Error: this records is NOT created it seems! (fe_groups:1)
Moreover, I have the same page tree as your installation steps and I also created a domain record on the "Your Shop" page ... but when I browse to the site, I get a blank page. The title (tag) on the browser tab is correct and viewing source does show some code, but the content is blank. I was under the impression that I would get a default template much like http://typo3.demo.aimeos.org/demo/ ... is that not the case? Or is this a problem with the page tree being a 18.10.x tree whereas I'm running 19.4.x?


Thanks again for the help!

User avatar
aimeos
Administrator
Posts: 3114
Joined: 01 Jan 1970, 00:00

Re: Field missing in database upon .t3d Import

Post by aimeos » 22 May 2019, 19:16

There no perfectly fitting page tree for the combination TYPO3 8.7 and Aimeos 19.x yet. However, you can use the 18.10 page tree and adapt it. The main thing you have to look at is the page layout (edit page -> Appearance). Using the page tree will add a shop similar to the demo but not the same. For this, you have to use the Aimeos TYPO3 distribution.
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, Image give us a star

superscotty19
Posts: 90
Joined: 13 May 2019, 08:09

Re: Field missing in database upon .t3d Import

Post by superscotty19 » 28 May 2019, 07:39

Sorry, I wasn't worried about the page tree - I was just wondering if the error was something to worry about. Otherwise, the page tree actually looks pretty good, even though there's a version mismatch.

My main concern is the template; I'll elaborate more on the "blank page". I took a T3 install and created a new page tree, then imported the page tree .t3d. I assumed that .t3d will include the necessary TYPOscript tenmplate constants/setup to define the HTML/Fluid templates/locations, because the demo shop located at http://typo3.demo.aimeos.org/demo/ obviously has some form of HTML/fluid template (gold buttons, lines, arial font, etc.) and https://aimeos.org/docs/Developers/Them ... ndamentals seems to suggest there is a default theme. However, in the "blank page", when I view source it is loading things but there's no HTML/fluid template/markers so nothing is being displayed. Moreover, the root page for the shop tree only has the following TYPOscript:

CONSTANTS:

Code: Select all

BASE_URL = https://shop.domain.com/
SETUP:

Code: Select all

# Hint: Change page ID to your "My Account" page here
config.typolinkLinkAccessRestrictedPages = 153
config.typolinkLinkAccessRestrictedPages_addParams = &return_url=###RETURN_URL###

# To enable customers to login, you need to add these TypoScript to your installation:
plugin.tx_aimeos.settings.client.html.email.from-name = My Demo Shop
plugin.tx_aimeos.settings.client.html.email.from-email = support@domain.com
# PID of the "Users" sysfolder so users can log in into accounts created by Aimeos
plugin.tx_aimeos.settings.mshop.customer.manager.typo3.pid-default = 157

# Prevents cross site scripting but don't works with all extensions
#config.additionalHeaders = Content-Security-Policy: default-src 'self'; img-src 'self' data:; style-src 'self' 'unsafe-inline'

# Required for correct language handling
config.language = de

# Remove smoothscroll code in boostrap_package so changing images in detail view works
page.includeJSFooterlibs.bootstrap_smoothscroll >

# Disable basket caching for development
# plugin.tx_aimeos.settings.client.html.basket.cache.enable = 0


# Default user groups for newly created user accounts by Aimeos after checkout
plugin.tx_aimeos.settings.controller.frontend.customer.groupids {
  0 = 2
}

# Use alternative image partial for detail pages
# plugin.tx_aimeos.settings.client.html.catalog.detail.partials.image = catalog/detail/image-partial-bottom.php

plugin.tx_aimeos.settings.client.html.catalog.selection.type.color = radio
plugin.tx_aimeos.settings.client.html.catalog.selection.type.width = radio
plugin.tx_aimeos.settings.client.html.catalog.selection.type.length = radio
plugin.tx_aimeos.settings.client.html.catalog.attribute.type.sticker = input
plugin.tx_aimeos.settings.client.html.catalog.attribute.preselect.interval = 1

# Overwrite and add translations
#plugin.tx_aimeos.settings.i18n.de {
#  0 {
#    domain = client/code
#    string = sticker
#    trans = Sticker
#  }
#  1 {
#    domain = client/code
#    string = print
#    trans = Aufdruck
#  }
#  2 {
#    domain = client/code
#    string = interval
#    trans = Intervall
#  }
#  3 {
#    domain = client/code
#    string = demo-print-text
#    trans = Ihr Text
#  }
#  4 {
#    domain = client/code
#    string = custom
#    trans = Preis
#  }
#  5 {
#    domain = client/code
#    string = demo-custom-date
#    trans = Aktivierungsdatum
#  }
#}
plugin.tx_aimeos.settings.i18n.en {
  0 {
    domain = client/code
    string = sticker
    trans = Sticker
  }
  1 {
    domain = client/code
    string = print
    trans = Print
  }
  2 {
    domain = client/code
    string = interval
    trans = Interval
  }
  3 {
    domain = client/code
    string = demo-print-text
    trans = Your text
  }
  4 {
    domain = client/code
    string = custom
    trans = Price
  }
  5 {
    domain = client/code
    string = demo-custom-date
    trans = Activation date
  }
}
INCLUDES:

Code: Select all

Aimeos Shop Configuration (aimeos)
... so I figured that either the "Setup" or the "Include" tab would include the HTML template. Again, the documentation (wonderfully) declares in https://aimeos.org/docs/Developers/Them ... ndamentals there is a theme/template already built in, so .... where is it?

Thanks again,
-Scott.

User avatar
aimeos
Administrator
Posts: 3114
Joined: 01 Jan 1970, 00:00

Re: Field missing in database upon .t3d Import

Post by aimeos » 28 May 2019, 17:29

Theme is included but I guess you've added the Aimeos page tree to an new and empty TYPO3 installation. If that is true, you might use the Aimeos distribution instead which gives you a fully functional shop in five minutes (also available in the Extension Manager if you select "Get preconfigured distribution" in the top left drop-down):
https://extensions.typo3.org/extension/aimeos_dist/

If you don't want to use the distribution, please make sure your installation already has a root page node that is set up correctly. Then, you can add the Aimeos page tree below that root page.
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, Image give us a star

superscotty19
Posts: 90
Joined: 13 May 2019, 08:09

Re: Field missing in database upon .t3d Import

Post by superscotty19 » 29 May 2019, 08:29

OHHH!!!!

I thought the distribution was an full aimeos AND TYPO3 installation, so I didn't install it!

To anyone reading along, here's why all this is happening. Assuming you have an existing T3 install/site on 8.7.x, you can install Aimeos like this:
1.) Install bootstrap_package 8.0.7
2.) install aimeos 18.10.8
- After download/install, click the gear and:
- Basic tab:
- demo data: overwrite
- After download/install, click the recyle icon to the right of aimeos to run the update script
3.) THEN install aimeos distribution 18.4.0

I now have a perfect page tree with templates, installed in 5 minutes as promised :-)

New problem: Every link I click (ex. detail or my account) takes me right back to the base url (shop.domain.com). Real_URL is installed and working.

Thank you very much for holding my hand on this one :-P
-Scott.

superscotty19
Posts: 90
Joined: 13 May 2019, 08:09

Re: Field missing in database upon .t3d Import

Post by superscotty19 » 30 May 2019, 00:26

UPDATE!

The problem was, there was a "localhost" domain record attached to the "My Shop" page. It must've been conflicting with the shop.domain.com domain record I created because as soon as I hid "localhost", all links worked.

That said, I now have a fully working system and, wow, this thing is HUGE. This is gonna be fun :-)

Thank you for such great support!
-Scott.

Post Reply