- Posts: 2
- Thank you received: 0
Kunena 7.0.4 Released
The Kunena team has announce the arrival of Kunena 7.0.4 [K 7.0.4] in stable which is now available for download as a native Joomla extension for J! 5.4.x/6.0.x. This version addresses most of the issues that were discovered in K 6.2 / K 6.3 / K 6.4 and issues discovered during the last development stages of K 7.0
Question Trying to fix an "XML Parsing Error" that is showing with a fresh install
- robemenecker
-
Topic Author
- Offline
- New Member
-
I just installed Kuneka 1.6, and am trying to troubleshoot an issue that was there right out of the gate. I am getting an:
XML Parsing Error at 1:1568. Error 4: not well-formed (invalid token)
This is appearing on my Kuneka forum pages at www.hairydogstaging1.com . You will need to log in to access the forums, as they are for Registered users only. To view, you can use the following demo login:
username: DemoUser
password: DemoUser
Once logged in, you will see the Members menu. Select Member Forums from the menu to go to the Kuneka forums area of the site.
Here is a copy-and-paste of my Report Configuration Settings output:
Database collation check: The collation of your table fields are correct
Legacy mode: Disabled | Joomla! SEF: Disabled | Joomla! SEF rewrite: Enabled | FTP layer: Enabled |
This message contains confidential informationhtaccess: Exists | PHP environment: Max execution time: 120 seconds | Max execution memory: 64M | Max file upload: 50M
Joomla default template details : hd_pmibaltimore | author: Barrie North w/ modifications by Rob Emenecker (Hairy Dog Digital) | version: 1.0.6 | creationdate: Sept 2009
Kunena version detailled: Installed version: 1.6.1 | Build: 3858 | Version name: Timu | Kunena detailled configuration:
Warning: Spoiler![th]Kunena config settings:[/th]
board_title Members’ Forum board_offline 0 board_ofset 0.00 offline_message <h2>The Forum is currently offline for maintenance.</h2>
<div>Check back soon!</div>enablerss 1 enablepdf 1 threads_per_page 20 messages_per_page 6 messages_per_page_search 15 showhistory 1 historylimit 6 shownew 1 jmambot 0 disemoticons 0 template default showannouncement 1 avataroncat 0 catimagepath category_images/ showchildcaticon 1 annmodid 62 rtewidth 450 rteheight 300 enableforumjump 1 reportmsg 1 username 1 askemail 0 showemail 0 showuserstats 0 showkarma 0 useredit 1 useredittime 0 useredittimegrace 600 editmarkup 1 allowsubscriptions 1 subscriptionschecked 1 allowfavorites 1 maxsubject 50 maxsig 300 regonly 0 changename 0 pubwrite 0 floodprotection 0 mailmod 0 mailadmin 0 captcha 0 mailfull 1 allowavatar 1 allowavatarupload 0 allowavatargallery 0 avatarquality 65 avatarsize 2048 allowimageupload 0 allowimageregupload 1 imageheight 800 imagewidth 800 imagesize 150 allowfileupload 0 allowfileregupload 1 filetypes txt,rtf,pdf,zip,tar.gz,tgz,tar.bz2 filesize 120 showranking 1 rankimages 1 avatar_src fb fb_profile fb pm_component no userlist_rows 30 userlist_online 1 userlist_avatar 1 userlist_name 1 userlist_username 1 userlist_posts 1 userlist_karma 1 userlist_email 0 userlist_usertype 0 userlist_joindate 1 userlist_lastvisitdate 1 userlist_userhits 1 latestcategory 0 showstats 1 showwhoisonline 1 showgenstats 1 showpopuserstats 1 popusercount 5 showpopsubjectstats 1 popsubjectcount 5 usernamechange 0 rules_infb 1 rules_cid 1 help_infb 1 help_cid 1 showspoilertag 1 showvideotag 1 showebaytag 1 trimlongurls 1 trimlongurlsfront 40 trimlongurlsback 20 autoembedyoutube 1 autoembedebay 1 ebaylanguagecode en-us fbsessiontimeout 1800 highlightcode 0 rss_type topic rss_timelimit month rss_limit 100 rss_included_categories rss_excluded_categories rss_specification rss2.0 rss_allow_html 1 rss_author_format name rss_author_in_title 1 rss_word_count 0 rss_old_titles 1 rss_cache 900 fbdefaultpage recent default_sort asc alphauserpointsnumchars 0 sef 1 sefcats 0 sefutf8 0 showimgforguest 1 showfileforguest 1 pollnboptions 4 pollallowvoteone 1 pollenabled 1 poppollscount 5 showpoppollstats 1 polltimebtvotes 00:15:00 pollnbvotesbyuser 100 pollresultsuserslist 1 maxpersotext 50 ordering_system mesid post_dateformat ago post_dateformat_hover datetime hide_ip 1 js_actstr_integration 0 imagetypes jpg,jpeg,gif,png checkmimetypes 1 imagemimetypes image/jpeg,image/jpg,image/gif,image/png imagequality 50 thumbheight 32 thumbwidth 32 hideuserprofileinfo put_empty integration_access communitybuilder integration_login communitybuilder integration_avatar communitybuilder integration_profile communitybuilder integration_private communitybuilder integration_activity communitybuilder boxghostmessage 0 userdeletetmessage 0 latestcategory_in 1 topicicons 1 onlineusers 1 debug 0 catsautosubscribed 0 showbannedreason 0 version_check 1 showthankyou 1 showpopthankyoustats 1 popthankscount 5 mod_see_deleted 0 bbcode_img_secure text listcat_show_moderators 1 lightbox 1 activity_limit 0
Third-party components: AlphaUserPoints: Disabled or not installed | CommunityBuilder: Installed (Version : 1.2.3) | Jomsocial: Disabled or not installed | UddeIm: Disabled or not installed
Plugins: System - Mootools12: Disabled | System - Mootools Upgrade: Disabled | JFirePHP: Disabled or not installed | Kunena Discuss: Disabled or not installed | Kunena Search: Disabled or not installed | My Kunena Forum Menu: Disabled or not installed | My Kunena Forum Posts: Disabled or not installed
Modules: Kunena Latest: Disabled or not installed | Kunena Stats: Disabled or not installed | Kunena Login: Disabled or not installed
Please Log in or Create an account to join the conversation.
- robemenecker
-
Topic Author
- Offline
- New Member
-
- Posts: 2
- Thank you received: 0
Oh, one other thing I want to mention is that the Mootools Upgrade is now installed. That did not make a difference.
So, I've solved the XML error. I had made a modification to the mod_mainmenu helper.php file that injected line endings to make for cleaner source code display. It did not like the whitespace element. I removed the line endings and now I do not get any XML Parsing Error, but I also DO NOT GET the Kunena menu.
Out of the fire, into the frying pan.
Please Log in or Create an account to join the conversation.
It's better to have a Kunena menu.
If you have already deleted the kunenamenu menu module, you should be able to recreate it by using the Create Menu feature in the Kunena control panel on your administrator site.
I would also refer you to Customised Menus in the Wiki.
Nice clean website, by the way, although it took me about 2 minutes to figure out how to login and find the forum ... so you might give some thought to reorganising it a little in this regard.
Blue Eagle vs. Crypsis reference guide
Read my blog and
Please Log in or Create an account to join the conversation.
When I then created a new module in the kunena_menu position with this, the XML error disappeared. Not sure what exactly caused it but maybe this is of help to some others too.
Cheers!
Please Log in or Create an account to join the conversation.
- Blogmudgeon
-
- Offline
- Junior Member
-
- Never a dull moment...
- Posts: 28
- Thank you received: 4
In general, the resolution of the issue is summed up in the last couple pages of this thread:
www.kunena.org/forum/168-k-16-support/63...not-have-kunena-menu
Irrespective of whether the menu works "out of the box" at some point there is going to be a conflict between the identically named aliases. The best course is to follow the instructions given in the above thread--and both Kunena menu and parsing/token error issues will disappear.
73 de Patrick
Joomla! 1.5.22
JomSocial 1.8.11
Kunena 1.6.1
EasyBlog 1.1.116
Please Log in or Create an account to join the conversation.
XML Parsing Error at 1:7104. Error 4: not well-formed (invalid token)
THIS error only appears on the top tabs which call up the kunena forum.
And when I disable mod kunena_menu the error message also disappears. Any ideas. Oh it appeared suddenly for no apparent reason.
here is one of the affected pages: www.fastingconnection.com/forum/main-index
Would appreciate any help. Running latest version of joomla 1.5 and latest kunena
Please Log in or Create an account to join the conversation.