This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit ezplatform.com

eZ Community » Forums » eZ Publish 5 Platform » EZ Publish 5.3 - Problems with...
expandshrink

EZ Publish 5.3 - Problems with integration from 5.2

EZ Publish 5.3 - Problems with integration from 5.2

Wednesday 11 June 2014 1:08:05 pm - 2 replies

Hi,
we are in the middle of moving to ez 5.3. We discovered some troubles with API changes with our projects.

1. ROUTING

Interface changed for UrlAliasRouter class, so we needed to adjust our default router.

services.xml
Before:
<service id="ses_routers.default_router" class="%ses_routers.default_router.class%">   
<argument type="service" id="ezpublish.api.repository.lazy" />   
<argument type="service" id="ezpublish.urlalias_generator" />   
<argument type="service" id="router.request_context" />   
<argument type="service" id="logger" />   
<call method="setContainer">       
<argument type="service" id="service_container" />   
</call>   
<tag name="router" priority="250" />
</service>
After:
<service id="ses_routers.default_router" class="%ses_routers.default_router.class%">   
<argument type="service" id="ezpublish.api.service.location"/>   
<argument type="service" id="ezpublish.api.service.url_alias"/>   
<argument type="service" id="ezpublish.urlalias_generator"/>   
<argument type="service" id="router.request_context" />   
<argument type="service" id="logger" />   
<call method="setConfigResolver">       
<argument type="service" id="ezpublish.config.resolver.chain"/>   
</call>
<tag name="router" priority="250" />
</service>    
  
2. DATABASE 
Added table for PDO session handling:
CREATE TABLE `session` (
`session_id` varchar(255) NOT NULL,
`session_value` text NOT NULL,
`session_time` int(11) NOT NULL,
PRIMARY KEY (`session_id`))
ENGINE=InnoDB DEFAULT CHARSET=utf8

Please share your experience in other fields.
Best regards,
Tomasz Jasek 

Thursday 12 June 2014 10:14:22 am

Hi Tomasz

One prominent enhancement breaking backwards compatibility is the Location Search in Search Service, as discussed in this post and this issue. It brings back the search logic we know from eZ 4 which focuses on locations (nodes) rather than content (objects).

Finally there are major configuration changes you are certainly aware of.

Cheers,
Donat

Thursday 12 June 2014 4:16:27 pm

Hi,

note that constructor functions are not considered as API, it is rather internal implementation details.
So this is rather a general (in software development in general) issue you'll always have to deal with from time to time when you extend internal classes rather then implementing public interfaces.

In this case I think there already is an interface you can implement, and if what your doing in the extended class is of general interest, we are of course open for changes/enhancements so you don't end up with this issue happy.gif Emoticon

 

Best,
André

Modified on Thursday 12 June 2014 4:35:45 pm by André R

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from