baseurl

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!
User avatar
aimeos
Administrator
Posts: 7889
Joined: 01 Jan 1970, 00:00

Re: baseurl

Post by aimeos » 16 Dec 2018, 13:01

Thanks, the workaround has been added to the scheduler base class and will be part of the next release:
https://github.com/aimeos/aimeos-typo3/ ... 253e34b960
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, Image give us a star

stiller
Posts: 88
Joined: 05 Mar 2016, 15:59

Re: baseurl

Post by stiller » 04 Jan 2019, 13:42

thank you. the workaround does the trick for me.

but there seems to be a problem with jsonapi in typo3 version newer than 8.7.18 as well
it is probably related.
update of the mini basket is not working after typo3 update to 8.7.22

I'm not getting any error messages

how can I debug the jsonapi output?

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

Re: baseurl

Post by aimeos » 07 Jan 2019, 12:31

Open the web inspector of your browser (e.g. Ctrl+Shift+J for Chrome) and look into the network tab. There are the requests and responses, esp. the XHR ones you can inspect.
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, Image give us a star

stiller
Posts: 88
Joined: 05 Mar 2016, 15:59

Re: typo3 version // json

Post by stiller » 09 Jan 2019, 15:39

well
thanks for guiding me through this.
in the chrome developer tools I can find 200 responses for
/warenkorb/ --- the basket page
/jsonapi/

the request for
/jsonapi/r/basket/ is missing.
when I type the url manually in the browser address field I'm receiving a complete json respond

how can I proceed?
is there a php restriction at work?

stiller
Posts: 88
Joined: 05 Mar 2016, 15:59

problem with jsonapi

Post by stiller » 10 Jan 2019, 15:46

I've figured out now that the problems are caused by an incompatibility between aimeos and the common cookies extension which is also using jsonapi.
Sorry. I didn’t think of it first because cookies was introduced together with a typo3 update and some other extension updates.
as jsonapi certainly is not my bag, I can't even say which implantation is faulty other whether this is a problem in general.
if you have no other proposal, I would try to switch to another cookie extension although there are very few with comparable scope of functions

cheers
Volker

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

Re: baseurl

Post by aimeos » 11 Jan 2019, 10:34

Can you tell us more about the incompatibility? What happens exactly?
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, Image give us a star

stiller
Posts: 88
Joined: 05 Mar 2016, 15:59

jsonapi

Post by stiller » 17 Jan 2019, 22:13

I did change the jsonapi url.
everything works fine now

stiller
Posts: 88
Joined: 05 Mar 2016, 15:59

problem with jsonapi

Post by stiller » 15 Feb 2019, 12:06

hi there

I must come back to this as I've figured out it is not solved at all.
it probably makes sense to open a new thread for this as it is not related to the original topic

anyway. problem is not caused by specific extensions but by an object added to the page object.
something like

page.25 = TEXT
page.25.value = hello world

does interfere with the json object and all json output
eg mini basket, out customers bought ...
won't come through

any solution for this?
cheers
Volker

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

Re: baseurl

Post by aimeos » 15 Feb 2019, 13:44

Make sure you remove it in the extension template of the page that contains the Aimeos JSON REST API plugin again.
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, Image give us a star

stiller
Posts: 88
Joined: 05 Mar 2016, 15:59

jsonapi

Post by stiller » 15 Feb 2019, 20:20

ok.
it comes from a different
I've inserted
page >
above the recommended
page {
typeNum = 0
headerData >
config {
disableAllHeaderCode = 1
disableCharsetHeader = 1
disablePrefixComment = 1
}
10 = CONTENT
10 {
table = tt_content
select.orderBy = sorting
select.languageField = sys_language_uid
}
}

tt_content.stdWrap >
tt_content.list = COA
tt_content.list.20 = CASE
tt_content.list.20.key.field = list_type
tt_content.list.templateName >
tt_content.list.templateRootPaths >
tt_content.list.partialRootPaths >
tt_content.list.layoutRootPaths >

Now it seems to work
thanks

Post Reply