Hi!
Could you show us your index.tpl file?
Regards,
Garvin
XML/RPC link
-
garvinhicking
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Re: XML/RPC link
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
Re: XML/RPC link
Hi,
I'm the "template admin" of Oliver and he asked me to get involved into this discussion in order to prevent further confusion. First of all: I don't know s9y, but I know PHP, Smarty, XHTML, CSS, JavaScript, ... so don't be afraid to point me to some technical documentation or code to read.
The template as I found it when Oliver first asked me to make some modifications was already heavily modified and there is no frontend_header hook in the head section. I tried placing the frontend_header hook in it, but that prints a DOCTYPE declaration in the middle of other tags that should be in <head>. I've then looked and found the "<link rel="EditURI"..." and as I think this is the line that should point XML-RPC clients to the right API endpoint I've just copied that into the static code. However Oliver says it is still not working for him. I've now just added the frontend_header hook, ignoring the invalid output (well, the xhtml contains a lot of errors anyway). I fear it's not easily possible to debug that blog system as it contains really a lot of modifications, so maybe I should try to find some time to rewrite the whole template and look at the plugins in order to get a "clean" system again.
Michael
I'm the "template admin" of Oliver and he asked me to get involved into this discussion in order to prevent further confusion. First of all: I don't know s9y, but I know PHP, Smarty, XHTML, CSS, JavaScript, ... so don't be afraid to point me to some technical documentation or code to read.
The template as I found it when Oliver first asked me to make some modifications was already heavily modified and there is no frontend_header hook in the head section. I tried placing the frontend_header hook in it, but that prints a DOCTYPE declaration in the middle of other tags that should be in <head>. I've then looked and found the "<link rel="EditURI"..." and as I think this is the line that should point XML-RPC clients to the right API endpoint I've just copied that into the static code. However Oliver says it is still not working for him. I've now just added the frontend_header hook, ignoring the invalid output (well, the xhtml contains a lot of errors anyway). I fear it's not easily possible to debug that blog system as it contains really a lot of modifications, so maybe I should try to find some time to rewrite the whole template and look at the plugins in order to get a "clean" system again.
Michael
-
garvinhicking
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Re: XML/RPC link
Hi michitux!
Thanks a lot for joining in. Could you provide the current index.tpl? And show a place where you inserted the frontend_header call? Basically this should never contain another "Doctype" output or whatever, so I think something might've went wrong here.
Possible causes for this could also be possible "Page Nugget" event plugins placed in s9y, which Oliver has seem to have enabled:
Best regards,
Garvin
Thanks a lot for joining in. Could you provide the current index.tpl? And show a place where you inserted the frontend_header call? Basically this should never contain another "Doctype" output or whatever, so I think something might've went wrong here.
Possible causes for this could also be possible "Page Nugget" event plugins placed in s9y, which Oliver has seem to have enabled:
So Oliver should check what exactly gets emitted inside this plugin, maybe it has the doctype, and let's go from there.Sample!
Beinhaltet HTML-Code der im HEAD-Bereich des Blogs eingebunden werden kann, z.B. für Meta-Tags oder JavaScripts.
version: 1.3
Best regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
-
garvinhicking
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Re: XML/RPC link
Hi!
One addition: the editUri actually SHOULD provide the XML-RPC editors to work properly, even with the "garbaged" template output right now.
Oliver, did you maybe try to upgrade the xml-rpc plugin to Grischas latest version? Maybe this solves things for you, since it is a major upgrade.
One addition: the editUri actually SHOULD provide the XML-RPC editors to work properly, even with the "garbaged" template output right now.
Oliver, did you maybe try to upgrade the xml-rpc plugin to Grischas latest version? Maybe this solves things for you, since it is a major upgrade.
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
Re: XML/RPC link
The plugin was updated.
My tech also added something to the header so that it works now, thanks.
We massively fiddled with the html of the template so we are not sure how to get this together with Template updates from SPARTACUS.
We might want to move our changes into plugins, but that seems a lot of work
My tech also added something to the header so that it works now, thanks.
We massively fiddled with the html of the template so we are not sure how to get this together with Template updates from SPARTACUS.
We might want to move our changes into plugins, but that seems a lot of work