Question Trouble upgrading to 1.7.1

I recently applied the 1.7.1 upgrade to a 1.7.3 Joomla! site using the extension manager. From there the update appeared to go fine, I got a success message with no errors.

However, when I wen to the Kunena component and did the DB upgrade, I got an error message saying something couldn't be written, then I got a success message just above it and all elements below listed as OK.

The forum seems to be up and working. Here is a copy of the Report Configuration Settings. How can I tell if the upgrade actually did work even though I got an error message?

Database collation check: The collation of your table fields are correct

Legacy mode: Disabled | Joomla! SEF: Enabled | Joomla! SEF rewrite: Disabled | FTP layer: Disabled |

This message contains confidential information

htaccess: Exists | PHP environment: Max execution time: 130 seconds | Max execution memory: 32M | Max file upload: 50M

Joomla default template details : beez_20 | author: Angie Radtke | version: 1.7.0 | creationdate: 25 November 2009

Kunena default template details : Blue Eagle (default) | author: Kunena Team | version: 1.7.1 | creationdate: 2011-11-16

Kunena version detailled: Installed version: 1.7.1 | Build: 5162 | Version name: UnderUret | Kunena detailled configuration:

Warning: Spoiler!

[th]Kunena config settings:[/th]

board_offline	0
board_ofset	0.00
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	1
showkarma	1
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	60
mailmod	0
mailadmin	0
captcha	0
mailfull	1
allowavatar	1
allowavatarupload	1
allowavatargallery	1
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
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	auto
integration_login	auto
integration_avatar	auto
integration_profile	auto
integration_private	auto
integration_activity	auto
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
show_list_time	720
show_session_type	0
show_session_starttime	0
userlist_allowed	0
userlist_count_users	1
enable_threaded_layouts	0
category_subscriptions	post
topic_subscriptions	every
pubprofile	1
thankyou_max	10
email_recipient_count	0
email_recipient_privacy	bcc
email_visible_address
captcha_post_limit	0

Third-party components: None

Third-party SEF components: None

Plugins: System - Mootools Upgrade: Disabled | System - Mootools12: Disabled

Modules: None

Hello,

Can-you put here the exact error message which was displayed, else i can't determine the source of the issue.

Unfortunately I can't. I didn't have the presence of mind to write it down or take a screenshot prior to changing screens. And now it's been a couple days so my memory is fuzzy.

I could probably manually install the update again and try to re-run it to see if it happens again. I've just not got that far yet. (not a big deal as the board isn't being used yet).

If this isn't a big deal and it's not causing you any immediate problems then I think we'll just park this topic in the archives until we have more information. Thanks for letting us know.

It's not a big deal, but enough to bug me.
I took some time to re-install. I simply used the extension manager to upload the zip file (instead of using the Update tab where it's no longer available). After the upload it took me to the Kunena window to either re-install or remove:





I clicked on the Green - Re-Install Kunena button. It progressed very quickly. It flashed one screen before the final one, but the error message remained. It first flashes the error "Unable to write entry" in the red banner. Then it very quickly refreshes the screen with the blue "installation completed successfully" banner with the previous error below it. Here is a screenshot:





So there we have it. It did it twice, same way. Any ideas?

So I decided to go a different route and see what happens. I uploaded 1.7.1 again and selected Uninstall. After that, I uploaded again and it brought me to the install screen here:



After that, it appears to have been successful:



It was okay for me to do this, since I'm still building the site and not letting anyone register yet. however, had this been a real live site, it would be nice to know why the upgrade gave that error message. Except at this point I've probably removed whatever the problem was by doing the uninstall so I won't be able to help with any additional troubleshooting.

Unable to write entry seems to come from file permission error.

Matias wrote: Unable to write entry seems to come from file permission error.

Do you mean a permission error -inside- the database that prevented a field from being written to?

That's the only thing that would make any sense, since after I deleted the data using the uninstall, I presume all the Kunena fields were removed. Then when I did the new install, it started fresh.

I didn't make any permissions changes between when it didn't work and when it did. The only difference was uninstalling then re-installing fresh.

Are you thinking it was some kind of database field-based permission in the database, like on one specific field and once it was deleted it fixed the problem?

Matias wrote "... file permission" See Securing Kunena

I don't mean to belabor the fact, but....
That makes no sense in this case.

I did not change any file (or directory) permissions between the time it didn't work and the time it did. So please, please, please, please... explain to me how this could have been a file permissions problem?

Let me re-cap:
- Ran an upgrade to an installed Kunena forum and got the error.
- Ran the installer again and selected Un-install.
- Ran the installer again and selected Install (fresh) and got no problem.

At no time did I change -any- permissions on any files or directories.

So you are telling me that some -file- Kunena installed previously wasn't allowing it to be updated because of a permission problem? But after it was deleted (via the uninstall?) it magically re-installed with the correct permissions? I guess I can buy that, but how did that permission change, and on what file? And if the permission was wrong, how come the uninstall was able to delete it?