w.bloggar & tikiwiki Posted by paulap01 30 Jan 2004 21:50 GMT-0000 posts: 112 Is there any documentation out there how w.bloggar and tikiwiki must be configured to work together. User account, URL, type,... I'am currently using XOOPS together with w.bloggar. And it works great. paulap
Posted by paulap01 30 Jan 2004 22:10 GMT-0000 posts: 112 I have try it (to set w.bloggar) I add an user account and get following error-message from w.bloggar: ...Unable to parse the XML response. Parser reason: Can't find path...ressource DTD/xhtml1-transitional.dtd paulap
Posted by Damian Parker 30 Jan 2004 22:30 GMT-0000 posts: 2881 > paulap01: > I have try it (to set w.bloggar) > > I add an user account and get following error-message from w.bloggar: > > ...Unable to parse the XML response. Parser reason: Can't find path...ressource DTD/xhtml1-transitional.dtd > > paulap type bloggar into the Search Wiki PageName box 😀 and choose the wbloggar page
Posted by paulap01 30 Jan 2004 22:56 GMT-0000 posts: 112 > Damian: > > paulap01: > > I have try it (to set w.bloggar) > > > > I add an user account and get following error-message from w.bloggar: > > > > ...Unable to parse the XML response. Parser reason: Can't find path...ressource DTD/xhtml1-transitional.dtd > > > > paulap > > type bloggar into the Search Wiki PageName box 😀 and choose the wbloggar page Thank you Damian, I have found the WikiPage and it works partly. Following questions: 1. I can only select blogs, not other komponents like article or wiki 2. I'am german speaking and the special characters like öäü are wrong interpreted. It seems a problem with the language-code 3. Does the XMLPRC - functionality support categories? thx in advance paulap
Posted by Damian Parker 31 Jan 2004 01:27 GMT-0000 posts: 2881 > paulap01: > Thank you Damian, > > I have found the WikiPage and it works partly. > > Following questions: > 1. I can only select blogs, not other komponents like article or wiki Correct its just blogs. > 2. I'am german speaking and the special characters like öäü are wrong interpreted. It seems a problem with the language-code Is your PHP setup to something other than UTF-8 maybe? > 3. Does the XMLPRC - functionality support categories? I'm not a huge w.bloggar expert. I use it to post into some blogs I keep as work records from my XP laptop. The rest of the time i'm in mozzy posting. Categories are missing in our Blog Posts at the moment. I've adopted the BlogDev and I'd value feedback there for missing features from experienced Bloggers. Can you help me? Damian
Posted by paulap01 31 Jan 2004 08:32 GMT-0000 posts: 112 > Damian: > > paulap01: > > Thank you Damian, > > > > I have found the WikiPage and it works partly. > > > > Following questions: > > 1. I can only select blogs, not other komponents like article or wiki > > Correct its just blogs. > > > 2. I'am german speaking and the special characters like öäü are wrong interpreted. It seems a problem with the language-code > > Is your PHP setup to something other than UTF-8 maybe? > > > 3. Does the XMLPRC - functionality support categories? > > I'm not a huge w.bloggar expert. I use it to post into some blogs I keep as work records from my XP laptop. The rest of the time i'm in mozzy posting. > > Categories are missing in our Blog Posts at the moment. I've adopted the BlogDev and I'd value feedback there for missing features from experienced Bloggers. Can you help me? > > Damian > Thx. One more night session... ad 1.) OK ad 2.) I set default_charset in php.ini to utf-8 and iso-8859-1. But when I download with w.bloggar the blog-entries, I have the same problem. Instead "für" I get a "für". The problem is the xml-stream. We have always: xml version="1.0" encoding="UTF-8" as the startline. But it must look like: xml version="1.0" encoding="iso-8859-1" that it works with international charsets. With xoops 2.0 (see www.xoops.org) and the headline component, you can set the charset/int-code for each RSS-Stream. And then it works with all languages (charsets). Is there a posibility to change the startline or the charset per stream? If not, we need a field more when defining rss-streams and streaming via xmlrpc. ad 3.) I see. But I am not a blog expert, I am a senior consultant working with CMS, DM, Workflow and portal systems since more then 15 years. I help large accounts to find and implement leading products. Since 2 years I am watching open source software products for managing content and improve business processes. I know a lot of other systems (typo3, xoops, postnuke,...). I can help to set up a process to compare tikiwiki with other/commercial products and regarding the requirements of the users / customers. Furthermore I have experience and a human network to promote software products. Is this useful? paulap
Posted by Damian Parker 31 Jan 2004 09:56 GMT-0000 posts: 2881 > The problem is the xml-stream. We have always: > xml version="1.0" encoding="UTF-8" > as the startline. > But it must look like: > xml version="1.0" encoding="iso-8859-1" > that it works with international charsets. This can be tidied up with some new features in CVS > ad 3.) I see. But I am not a blog expert, I am a senior consultant working with CMS, DM, Workflow and portal systems since more then 15 years. I help large accounts to find and implement leading products. Since 2 years I am watching open source software products for managing content and improve business processes. I know a lot of other systems (typo3, xoops, postnuke,...). No worries 😉 > I can help to set up a process to compare tikiwiki with other/commercial products and regarding the requirements of the users / customers. Furthermore I have experience and a human network to promote software products. > > Is this useful? Of course! How do we compare? You could probably do with getting in touch with Marc Laporte UserPageMarcLaporte as he deals with our Tiki Marketing Damian
Posted by paulap01 31 Jan 2004 14:53 GMT-0000 posts: 112 > Damian: > > The problem is the xml-stream. We have always: > > xml version="1.0" encoding="UTF-8" > > as the startline. > > But it must look like: > > xml version="1.0" encoding="iso-8859-1" > > that it works with international charsets. > > This can be tidied up with some new features in CVS If you need help to describe the features, contact me. > > > ad 3.) I see. But I am not a blog expert, I am a senior consultant working with CMS, DM, Workflow and portal systems since more then 15 years. I help large accounts to find and implement leading products. Since 2 years I am watching open source software products for managing content and improve business processes. I know a lot of other systems (typo3, xoops, postnuke,...). > > No worries 😉 It's funny for me to work with this community. And tikiwiki has a lot of potential. With a new and better positioning for possible solutions and against the competitors it will be a shining star. A broad band of features is ok but only if the features are stable and well documented. The combination of wiki, blog and the other modules are a real advantage. But i think there are too many features without a clear understanding of the business advantages. > > > I can help to set up a process to compare tikiwiki with other/commercial products and regarding the requirements of the users / customers. Furthermore I have experience and a human network to promote software products. > > > > Is this useful? > > Of course! How do we compare? You could probably do with getting in touch with Marc Laporte UserPageMarcLaporte as he deals with our Tiki Marketing > I will contact Marc Laporte and try to support. Concerning the comparision I will add a new topic in this forum. What i see is, that we need enhancements and more cooperation between the components. For instance: I will descibe a criteria with wiki, will rank the importance, will have the possibility to level on a new page the feature of a product against the requirement,... thx paulap > Damian
Posted by Damian Parker 30 Jan 2004 22:30 GMT-0000 posts: 2881 > paulap01: > I have try it (to set w.bloggar) > > I add an user account and get following error-message from w.bloggar: > > ...Unable to parse the XML response. Parser reason: Can't find path...ressource DTD/xhtml1-transitional.dtd > > paulap type bloggar into the Search Wiki PageName box 😀 and choose the wbloggar page
Posted by paulap01 30 Jan 2004 22:56 GMT-0000 posts: 112 > Damian: > > paulap01: > > I have try it (to set w.bloggar) > > > > I add an user account and get following error-message from w.bloggar: > > > > ...Unable to parse the XML response. Parser reason: Can't find path...ressource DTD/xhtml1-transitional.dtd > > > > paulap > > type bloggar into the Search Wiki PageName box 😀 and choose the wbloggar page Thank you Damian, I have found the WikiPage and it works partly. Following questions: 1. I can only select blogs, not other komponents like article or wiki 2. I'am german speaking and the special characters like öäü are wrong interpreted. It seems a problem with the language-code 3. Does the XMLPRC - functionality support categories? thx in advance paulap
Posted by Damian Parker 31 Jan 2004 01:27 GMT-0000 posts: 2881 > paulap01: > Thank you Damian, > > I have found the WikiPage and it works partly. > > Following questions: > 1. I can only select blogs, not other komponents like article or wiki Correct its just blogs. > 2. I'am german speaking and the special characters like öäü are wrong interpreted. It seems a problem with the language-code Is your PHP setup to something other than UTF-8 maybe? > 3. Does the XMLPRC - functionality support categories? I'm not a huge w.bloggar expert. I use it to post into some blogs I keep as work records from my XP laptop. The rest of the time i'm in mozzy posting. Categories are missing in our Blog Posts at the moment. I've adopted the BlogDev and I'd value feedback there for missing features from experienced Bloggers. Can you help me? Damian
Posted by paulap01 31 Jan 2004 08:32 GMT-0000 posts: 112 > Damian: > > paulap01: > > Thank you Damian, > > > > I have found the WikiPage and it works partly. > > > > Following questions: > > 1. I can only select blogs, not other komponents like article or wiki > > Correct its just blogs. > > > 2. I'am german speaking and the special characters like öäü are wrong interpreted. It seems a problem with the language-code > > Is your PHP setup to something other than UTF-8 maybe? > > > 3. Does the XMLPRC - functionality support categories? > > I'm not a huge w.bloggar expert. I use it to post into some blogs I keep as work records from my XP laptop. The rest of the time i'm in mozzy posting. > > Categories are missing in our Blog Posts at the moment. I've adopted the BlogDev and I'd value feedback there for missing features from experienced Bloggers. Can you help me? > > Damian > Thx. One more night session... ad 1.) OK ad 2.) I set default_charset in php.ini to utf-8 and iso-8859-1. But when I download with w.bloggar the blog-entries, I have the same problem. Instead "für" I get a "für". The problem is the xml-stream. We have always: xml version="1.0" encoding="UTF-8" as the startline. But it must look like: xml version="1.0" encoding="iso-8859-1" that it works with international charsets. With xoops 2.0 (see www.xoops.org) and the headline component, you can set the charset/int-code for each RSS-Stream. And then it works with all languages (charsets). Is there a posibility to change the startline or the charset per stream? If not, we need a field more when defining rss-streams and streaming via xmlrpc. ad 3.) I see. But I am not a blog expert, I am a senior consultant working with CMS, DM, Workflow and portal systems since more then 15 years. I help large accounts to find and implement leading products. Since 2 years I am watching open source software products for managing content and improve business processes. I know a lot of other systems (typo3, xoops, postnuke,...). I can help to set up a process to compare tikiwiki with other/commercial products and regarding the requirements of the users / customers. Furthermore I have experience and a human network to promote software products. Is this useful? paulap
Posted by Damian Parker 31 Jan 2004 09:56 GMT-0000 posts: 2881 > The problem is the xml-stream. We have always: > xml version="1.0" encoding="UTF-8" > as the startline. > But it must look like: > xml version="1.0" encoding="iso-8859-1" > that it works with international charsets. This can be tidied up with some new features in CVS > ad 3.) I see. But I am not a blog expert, I am a senior consultant working with CMS, DM, Workflow and portal systems since more then 15 years. I help large accounts to find and implement leading products. Since 2 years I am watching open source software products for managing content and improve business processes. I know a lot of other systems (typo3, xoops, postnuke,...). No worries 😉 > I can help to set up a process to compare tikiwiki with other/commercial products and regarding the requirements of the users / customers. Furthermore I have experience and a human network to promote software products. > > Is this useful? Of course! How do we compare? You could probably do with getting in touch with Marc Laporte UserPageMarcLaporte as he deals with our Tiki Marketing Damian
Posted by paulap01 31 Jan 2004 14:53 GMT-0000 posts: 112 > Damian: > > The problem is the xml-stream. We have always: > > xml version="1.0" encoding="UTF-8" > > as the startline. > > But it must look like: > > xml version="1.0" encoding="iso-8859-1" > > that it works with international charsets. > > This can be tidied up with some new features in CVS If you need help to describe the features, contact me. > > > ad 3.) I see. But I am not a blog expert, I am a senior consultant working with CMS, DM, Workflow and portal systems since more then 15 years. I help large accounts to find and implement leading products. Since 2 years I am watching open source software products for managing content and improve business processes. I know a lot of other systems (typo3, xoops, postnuke,...). > > No worries 😉 It's funny for me to work with this community. And tikiwiki has a lot of potential. With a new and better positioning for possible solutions and against the competitors it will be a shining star. A broad band of features is ok but only if the features are stable and well documented. The combination of wiki, blog and the other modules are a real advantage. But i think there are too many features without a clear understanding of the business advantages. > > > I can help to set up a process to compare tikiwiki with other/commercial products and regarding the requirements of the users / customers. Furthermore I have experience and a human network to promote software products. > > > > Is this useful? > > Of course! How do we compare? You could probably do with getting in touch with Marc Laporte UserPageMarcLaporte as he deals with our Tiki Marketing > I will contact Marc Laporte and try to support. Concerning the comparision I will add a new topic in this forum. What i see is, that we need enhancements and more cooperation between the components. For instance: I will descibe a criteria with wiki, will rank the importance, will have the possibility to level on a new page the feature of a product against the requirement,... thx paulap > Damian
