Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Did you ever resolve this issue? I am getting Token expired during publishing in web 8.5 now as well , the Token seem to remain expired the even when the time stamp has changed and i get a transport service failure.
Your answer got me digging and I found this : The privileges and roles created for this user are the minimum requirements for database installation. Before you create a Content Manager database, run the SQL script CreateTridionSYSUser.sql (for example from SQL*Plus) located in the directory Database\Scripts\Oracle\Tools on your SDL Web installation media.Many thanks
The user needs rights for granting roles, e.g GRANT EXECUTE ON DBMS_SCHEDULER even if you have a SYSDBA account in the oracle world, you still need to have the Admin option. I think it does require some level of Admin, hence my question, if there is a list of privilledges that is required then maybe we can create an account with all those rights, not every organisation is wiling to give Admin rights in Production.
The upgrade was in stages, first from T2011 HR2 -> T2013 and then T2013 -> T2013 SP1 HR1 and then finally T2013SP1 HR1-> Web8.5. SDL provides scripts for each of these steps, so yes there is no direct upgrade from 2011 to web 8.5, but there is an indirect upgrade.
As described above, I have done the same in my .NET DD4T application .(Not DXA) that TBB adds the structure group metadata values into the published JSON and I just created a property in my Page Model class for it. It may be different in the Java.
I have updated my question and I am using Web8.5's Template builder, i am not getting this error when i try to create a bundle, i get a different error when i try to create a bundle which is simply unknown Virtual Folder Type: Virtual Folder Cartridge is not registered for this type.
If you already see it in the published JSON, I would expect that you should be able to map it explicitly in your defaultPageModel as property using DXA @SemanticPropety('field name')
