Stock level not in frontend anymore

Questions around the TYPO3 integration and plugins
Forum rules
Always add your TYPO3, Aimeos and PHP version as well as your environment (Linux/Mac/Win)
Spam and unrelated posts will be removed immediately!
Shopmister
Posts: 92
Joined: 15 Jan 2021, 11:02

Stock level not in frontend anymore

Post by Shopmister » 27 Mar 2021, 13:32

TYPO3 Version
10.4.13
Webserver
Apache
PHP Version
7.3.27-1~deb10u1
Database (Default)
MySQL 5.5.5-10.3.27-MariaDB-0+deb10u1
Application Context
Production
Operating System
Linux 4.19.0-9-amd64
Last Scheduler run
27-03-21 at 09:12, Duration 0 min, (started automatically)
Aimeos .6 and .7

I Have no idea how long. But what i know: Its not a Aimeos templateproblem...Okay i dont but i have the same Version at another site and there it works.
All other things works, what i can see
But now at list and deatailview arent stock level anymore. In Typoscript i have that:
# Define Stock Levels or turn Stock Levels Off

plugin.tx_aimeos.settings.client.html.catalog.stock.level.low = 3
plugin.tx_aimeos.settings.client.html.catalog.stock.level.high = 5

But i did set up a new installation and s the same

I scare for a bigger problem. The reason because i doint want the shop online before i have a solution for that problem :O

This Errors i have with so many others in the browserdevtools:
Die Ressource von "https://domain.eu/your-shop/shop/stock/ ... mo-voucher" wurde wegen eines MIME-Typ-Konfliktes ("text/html") blockiert (X-Content-Type-Options: nosniff).
And counts the same and some more different things in yellow
and this here: (btw in the folder arent any things)
https://domainname.de/uploads/tx_aimeos ... 144768.jpg

Uncaught SyntaxError: expected expression, got '<'
counts:1
Uncaught SyntaxError: expected expression, got '<'
stock:1

Ps. id disabled the mime type checking in htacces: #Header set X-Content-Type-Options "nosniff"
SOme errorsreports are away but the stocklevel isnt there :)

Thanks
Last edited by Shopmister on 02 Apr 2021, 10:12, edited 2 times in total.

Shopmister
Posts: 92
Joined: 15 Jan 2021, 11:02

Re: Stock level not in frontend anymore

Post by Shopmister » 01 Apr 2021, 12:30

TYPO3 Version
10.4.13
Webserver
Apache
PHP Version
7.3.27-1~deb10u1
Database (Default)
MySQL 5.5.5-10.3.27-MariaDB-0+deb10u1
Application Context
Production
Operating System
Linux 4.19.0-9-amd64
Last Scheduler run
27-03-21 at 09:12, Duration 0 min, (started automatically)
Aimeos .6 and .7

I Have no idea how long. But what i know: Its not a Aimeos templateproblem...Okay i dont but i have the same Version at another site and there it works.
All other things works, what i can see
But now at list and deatailview arent stock level anymore. In Typoscript i have that:
# Define Stock Levels or turn Stock Levels Off

plugin.tx_aimeos.settings.client.html.catalog.stock.level.low = 3
plugin.tx_aimeos.settings.client.html.catalog.stock.level.high = 5

But i did set up a new installation and s the same

I scare for a bigger problem. The reason because i doint want the shop online before i have a solution for that problem :O

This Errors i have with so many others in the browserdevtools:
Die Ressource von "https://domain.eu/your-shop/shop/stock/ ... mo-voucher" wurde wegen eines MIME-Typ-Konfliktes ("text/html") blockiert (X-Content-Type-Options: nosniff).
And counts the same and some more different things in yellow
and this here: (btw in the folder arent any things)
https://domainname.de/uploads/tx_aimeos ... 144768.jpg

Uncaught SyntaxError: expected expression, got '<'
counts:1
Uncaught SyntaxError: expected expression, got '<'
stock:1

Ps. id disabled the mime type checking in htacces: #Header set X-Content-Type-Options "nosniff"
SOme errorsreports are away but the stocklevel isnt there :)

Thanks
No idea? Or didnt see it :)

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

Re: Stock level not in frontend anymore

Post by aimeos » 02 Apr 2021, 17:01

Did you remove the Aimeos TypoScript from the root page? It's in:
Left navigation > Templates > Select page with globe > Edit the whole template record > Includes

The "Aimeos shop configuration (aimeos)" entry must be in the "Selected items" field.

Background: The Aimeos TypoScript defines that page to be of type "application/javascript":
- https://github.com/aimeos/aimeos-typo3/ ... up.txt#L35
- https://github.com/aimeos/aimeos-typo3/ ... xt#L61-L76
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, Image give us a star

Shopmister
Posts: 92
Joined: 15 Jan 2021, 11:02

Re: Stock level not in frontend anymore

Post by Shopmister » 05 Apr 2021, 10:34

Did you remove the Aimeos TypoScript from the root page? It's in:
Left navigation > Templates > Select page with globe > Edit the whole template record > Includes

The "Aimeos shop configuration (aimeos)" entry must be in the "Selected items" field.

Background: The Aimeos TypoScript defines that page to be of type "application/javascript":
- https://github.com/aimeos/aimeos-typo3/ ... up.txt#L35
- https://github.com/aimeos/aimeos-typo3/ ... xt#L61-L76
Thanks, All i did right. :)
But....
i think i found the problem:
The file rights wasnt right because the server inclusive install about typo3 set the rights newly of all files too:
rw-r--r-- (0644). And during installing AImeos seems to need some files with higher rights to can set some thing like the uploadfolder?

Its possible that that was the problem, that with the 0644 rights for all files, for aimeos during installation its not sossible to create the uploadfolder and some things that to be need for stockdata?

Its possible that the rights are the reason?

And when Aimeos do create the uploadfolder? After this time install the stock view works but the uploadfolder not there

Do you have a documentation about what rights have to given to the aimeos extensionfiles?

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

Re: Stock level not in frontend anymore

Post by aimeos » 06 Apr 2021, 15:12

To install the Aimeos extension in the typo3conf/ext folder in non-composer installations, your web server needs write permissions to typo3conf/ext and uploads folders.

In composer mode, your console user must be able to write into these directories and into the folder above the public directory. Composer installations are more sensitive to permission problems because the console user and the web server not necessarily share the same primary group and may use different permission settings.
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, Image give us a star

Post Reply