|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
| < Prev | 1 - 2 | Next > |
|
|
Publishing issueHI:
i am kinda new to this one. i want to publish a page but not the whole of the page (which include by default apache logo, menu on left, body of page and footer) . All i want is that all my new addition to a newly created document in KUPU editor should only and only be publish. means a i want to publish my document EXCEPT menus,header logo and footer(which are included by default). only content of my document should be published, any one can tell me how can i do that thanks |
|
|
Re: Publishing issueJay wrote:
> HI: > i am kinda new to this one. i want to publish a page but not the whole of > the page (which include by default apache logo, menu on left, body of page > and footer) . All i want is that all my new addition to a newly created > document in KUPU editor should only and only be publish. means a i want to > publish my document EXCEPT menus,header logo and footer(which are included > by default). only content of my document should be published, any one can > tell me how can i do that You have to setup some alternative pipelines in your publication sitemap, which match for a different extension, for instance /foo/bar.plain.html and don't include the menu, footer etc. in the aggregation. You have to rewrite the links accordingly. Be careful to use a dot as separator, so the document ID is recognized correctly. If you don't want the "traditional" view at all, you can just remove the navigation elements from the aggregation and change the XSLTs accordingly. -- Andreas -- Andreas Hartmann Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://lenya.apache.org andreas.hartmann@... andreas@... --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Publishing issueHi Jay
you'll have to make change in each of XSLT corresponding to your document, like page2xhtml.xslt, in which you can ommit these stuffs or can give your own images and all, so try to find the xlt used by ur document you can find it in publication_sitemap.xmap bhavya On 7/28/06, Jay <jabirfayyaz@...> wrote:
-- Thank you, Bhavya Sharma |
|
|
Re: Publishing issuethanks Bhavya and Andreas. i have disabled the following line
from publication-sitemap <map:aggregate element="cmsbody"> <map:part src="cocoon://navigation/{2}/{3}/map/{5}.xml"/> <!-- <map:part src="cocoon://navigation/{2}/{3}/breadcrumb/{5}.xml"/> --> <!-- <map:part src="cocoon://navigation/{2}/{3}/tabs/{5}.xml"/> --> <!-- <map:part src="cocoon://navigation/{2}/{3}/menu/{5}.xml"/> --> <!-- <map:part src="cocoon://navigation/{2}/{3}/search/{5}.xml"/> <map:part src="cocoon:/lenya-document-{1}/{3}/{4}/{page-envelope:document-path}"/> </map:aggregate> but this resulted in other way. menus, search etc etc vanished from inside lenya also, i want get rid of these object in my published document only, suppose i hav created a new doc named 'MyDoc' in default publication, can u specify the new pipeline which i should add in publication-sitemap to achieve my objects. thanks u very much |
|
|
Re: Publishing issueHi
Jay, try to create following pipeline in publication_sitemap.xmap and before the lenyabody pipeline , i am sure , its gonna to help you , as i have aleready done some time before lenya's main pipeline as you can see its a normal thing that i thinh you have done in Coccon <map:match pattern="**/**"> <map:match pattern="**/yourpage.html"> <map:generate src="your.xml"/> <map:transform src="yourl.xsl "> <map:serialize type="xml"/> </map:match> On 7/28/06, Jay <jabirfayyaz@...> wrote:
-- Thank you, Bhavya Sharma |
|
|
Re: Publishing issuewell tht works little bit Bhavya, thanks again for helping. now with your mentioned pipeline, my newly created document is transformed with my jay.xsl file, it removed default header+footer+menu. Now how can i publish this doc as all the menus are gone?????. my objective is to get final published document without menu+header+footer after editing it in Kupu while keeping everything intact before publishing.
|
|
|
Re: Publishing issueHi Jay, can you describe me in more details, as i could'nt get it properly
Bhavya On 7/28/06, Jay <jabirfayyaz@...> wrote:
-- Thank you, Bhavya Sharma |
|
|
Re: Publishing issueOk let me explain in detail. i am creating a document in lenya and doing some sort of editing in KUPU editor as well. thats the most easiest part ever in my Lenya Life :)
Now we can publish our documents with 'workflow->publish' this creates and html file with apache logo on it,menu on left plus footer(by default). but i dont want publishing like this. i only want to publish what i have edited in KUPU editor. only that part which i say content of new document should be published. when i am viewing my document in editor view,i should be able to again edit my document and publish it again and again, but when i see it in live view nothing should be displayed except document (no menu, no logo etc) remember i m only adding text to my page with kupu, and only text should be displayed in live view. i hope its clear, but if not please do ask me again. |
|
|
Re: Publishing issuelet me check this issue as have no idea
On 7/28/06, Jay <jabirfayyaz@...> wrote:
-- Thank you, Bhavya Sharma |
|
|
Re: Publishing issueOK :( im waiting for respone
|
|
|
Re: Publishing issueHi
I try to look at following link http://lenya.apache.org/1_2_x/how-to/custom_resourcetype.html i think it'll help you out bhavya On 7/28/06, Jay <jabirfayyaz@...> wrote:
-- Thank you, Bhavya Sharma |
|
|
Re: Publishing issuethanks, if u can locate which xsl or any other file really publishes our documents in lenya, then i think i can really take off.
|
|
|
Re: Publishing issueHi Jay i'd recommand you to contact you at
<solprovider@...>, <solprovider@...>, as they can suggest you more professionaly , also it is my office leaving time sorry i hope u'll get ur problem solve out bhavya On 7/28/06, Jay <jabirfayyaz@...> wrote:
-- Thank you, Bhavya Sharma |
|
|
Re: Publishing issuebundle of thanx to u, good bye
|
|
|
Re: Publishing issueHi Jay,
Which version of Lenya are you using? In 1.4 just reference the document with a different extension to access the raw content (replace the .html with .xml). HTH, --Doug Jay wrote: > HI: > i am kinda new to this one. i want to publish a page but not the whole of > the page (which include by default apache logo, menu on left, body of page > and footer) . All i want is that all my new addition to a newly created > document in KUPU editor should only and only be publish. means a i want to > publish my document EXCEPT menus,header logo and footer(which are included > by default). only content of my document should be published, any one can > tell me how can i do that > thanks --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Publishing issueim using Lenya 1.2.4. im looking for the listener of 'workflow->publish'. as i want only part of my document to be published not whole
|
|
|
Re: Publishing issueJay wrote:
> im using Lenya 1.2.4. im looking for the listener of 'workflow->publish'. as > i want only part of my document to be published not whole That is not an issue of the publishing process. You publish only the document source, not the navigation elements etc. Changing the publishing process won't solve your issue. The solution is to apply a different XSLT for the live area. -- Andreas -- Andreas Hartmann Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://lenya.apache.org andreas.hartmann@... andreas@... --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Publishing issuethanx alot Andreas, im taking too much of your time. Just to make it sure, is 'addSourceTag.xsl' is used in live view, which i should replace with my own xsl file??im talking about publication-sitemap file in root directory of default publication
<map:match pattern="live/**.html"> <map:transform src="../../xslt/authoring/edit/addSourceTags.xsl"> <map:parameter name="source" value="{global:cache-dir}/live/{1}.html"/> |
|
|
Re: Publishing issueJay wrote:
> thanx alot Andreas, im taking too much of your time. Just to make it sure, is > 'addSourceTag.xsl' is used in live view, which i should replace with my own > xsl file??im talking about publication-sitemap file in root directory of > default publication > > <map:match pattern="live/**.html"> > <map:transform > src="../../xslt/authoring/edit/addSourceTags.xsl"> > <map:parameter name="source" > value="{global:cache-dir}/live/{1}.html"/> No, that pipeline is only used to read from the cache. You have to add such a matcher to the general pipeline which builds the page. -- Andreas -- Andreas Hartmann Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://lenya.apache.org andreas.hartmann@... andreas@... --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Publishing issueBhavya - Thank you for the compliment.
I am now responsible for the external website of a Fortune 500 company, and have been busy learning how it works, and all the current and in-development applications for it. I still want to finish Lenya 1.3. When the new job started, I was working on adding an XHTML editor for flat content so the new storage structure is usable. (You can use 1.3's Module system with 1.2's storage structure, but that greatly reduces the improvements.) Once an editor is committed, I can start improving the functionality as documented in the TODO file. My weekdays are consumed by my job, and the weekends seem to disappear, so it may be a while. --- Jay, As others have suggested, there are several methods such as changing the extension if you want a "printable version" with just the content. Assuming you want exactly what you said... You want everything to work as normal in Lenya, except you want the live pages to show only the content without any navigation. This upsets the other devs because the dynamic navigation system is really good and they do not understand why anybody would not want to use it. I assume you have many websites with very few pages, and do not want to create a Publication for each (the Lenya way), or have them automatically link to each other (as the Lenya navigation does.) To make the change: FILE: publication-sitemap.xml Immediately after this line: <map:match pattern="lenyabody-*/*/*/*/**"> Add this: <map:match pattern="lenyabody-*/*/live/*/**"> <map:aggregate element="cmsbody"> <map:part src="cocoon:/lenya-document-{1}/live/{3}/{page-envelope:document-path}"/> </map:aggregate> <map:transform src="xslt/page2xhtml-{3}.xsl"> <map:parameter name="root" value="{page-envelope:context-prefix}/{2}/live"/> <map:parameter name="url" value="{4}"/> <map:parameter name="document-id" value="{page-envelope:document-id}"/> <map:parameter name="document-type" value="{page-envelope:document-type}"/> </map:transform> <map:transform type="i18n" label="debug"> <map:parameter name="locale" value="{page-envelope:document-language}"/> </map:transform> <map:select type="parameter"> <map:parameter name="parameter-selector-test" value="{1}"/> <map:when test="view"> <map:transform type="link-rewrite"/> </map:when> </map:select> <map:serialize type="xml"/> </map:match> </map:pipeline> The code is exactly the rest of the match, - wrapped with another match for only the "live" area, - without the navigation elements, - "{3}" replaced by "live", and - the numbered variables above 3 reduced by one. That produces the HTML without the navigation contents only for the "live" Area. In the above code, you may also want to change: <map:transform src="xslt/page2xhtml-{3}.xsl"> To something like: <map:transform src="xslt/page2xhtmlNoNav-{3}.xsl"> And create the appropriate XSLT files by copying the existing "xsl/page2xhtml-*.xsl" files and renaming them to "xsl/page2xhtmlNoNav-*.xsl". Then you can adjust the new files so they do not add the navigation elements or anything else undesirable. But then the HTML will not exactly match what appears while authoring. solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
| < Prev | 1 - 2 | Next > |
| Free embeddable forum powered by Nabble | Forum Help |