? ? Success

User tests: Successful: Unsuccessful:

avatar wilsonge
wilsonge
14 Jan 2016

To test ensure that Joomla itself functions the same (just try a couple of pages). The error page works and any custom formats you might have (e.g. the VCF view for com_contact etc).

There should be no changes before and after the patch, however in the future you can now autoload properly in JDocument. Having things like the renderers now running autoloading is going to be important in the future for introduction of alternate output formats.

Votes

# of Users Experiencing Issue
0/1
Average Importance Score
3.00

avatar wilsonge wilsonge - open - 14 Jan 2016
avatar wilsonge wilsonge - change - 14 Jan 2016
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 14 Jan 2016
Labels Added: ? ?
avatar izharaazmi
izharaazmi - comment - 15 Jan 2016

:+1: for adding support for JDocumentRenderer[doc-type][rendered-type]. How about now providing a standard set of JDocumentJson renderers? Should we?

avatar photodude photodude - test_item - 15 Jan 2016 - Tested successfully
avatar photodude
photodude - comment - 15 Jan 2016

I have tested this item :white_check_mark: successfully on aa7c947

As per test instructions, tested that Joomla itself functions the same


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8905.

avatar wilsonge
wilsonge - comment - 15 Jan 2016

@izharaazmi something like that won't be part of this PR. As long as people are extending the right classes (which we have checks for) then it's down to them to provide an implementation. In the future we could investigate some sort of interface. But it's likely going to be something JDocumentRenderer already supports anyhow

avatar izharaazmi
izharaazmi - comment - 15 Jan 2016

Yeah, I understand that that can't be part of this PR. I was asking for the additional prospects. I think we can provide a full fledged structured rendering similar to that of html renderers, like response code, messages, body, redirects, callbacks, etc or whatever we can figure out when into it.

This can give us a well defined format for Joomla based JSON APIs as well. Same can be done for XML rendering for XML APIs.

I understand that this is not the part of Joomla project scope right now. But I wonder, what if?

Btw, JDocumentJSON right now appears to be just a barebone (sorry! I may be wrong here). It renders the output with Content-Disposition: attachment anyway, which usually is not helpful always.
However, these can be discussed later in case we actually decide to work on this.

avatar wilsonge
wilsonge - comment - 15 Jan 2016

Exactly. There's definitely a lot of work to do with JDocument. I see this as the start of getting a lot of these issues fixed up

avatar mbabker
mbabker - comment - 15 Jan 2016

JDocument and its subclasses aren't a proper request/response structure, nor even responsible for building the response. It is at best a page rendering system; all of the response data is handled as part of the JApplicationWeb API. JDocument does have a couple of calls into the application to set some response data based on the format, but that's the extent of what it's capable of at the moment.

avatar anibalsanchez anibalsanchez - test_item - 15 Jan 2016 - Tested successfully
avatar anibalsanchez
anibalsanchez - comment - 15 Jan 2016

I have tested this item :white_check_mark: successfully on aa7c947

I have been working with this patch, it works OK.


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8905.

avatar wilsonge wilsonge - change - 15 Jan 2016
Status Pending Closed
Closed_Date 0000-00-00 00:00:00 2016-01-15 20:13:10
Closed_By wilsonge
avatar wilsonge wilsonge - reference | 06200e9 - 15 Jan 16
avatar wilsonge wilsonge - merge - 15 Jan 2016
avatar wilsonge wilsonge - close - 15 Jan 2016
avatar mbabker mbabker - head_ref_deleted - 15 Jan 2016

Add a Comment

Login with GitHub to post a comment