kavadas
commented
11 years ago Hi. Can you please install the development version and see if the issue remains? You can get it at http://getk2.org/assets/get
Closed rotech1 closed 8 years ago
kavadas
commented
11 years ago Hi. Can you please install the development version and see if the issue remains? You can get it at http://getk2.org/assets/get
rotech1
commented
11 years ago Not working… can’t install.
Upload & install ( the zip file) gives me error: -1 - An error has occurred.
Copy failed
Install from URL gives : Unable to find install package
Install from directory:
-1 - An error has occurred.
Copy failed
The /tmp/ folder has the zip uload, plus K2 installation folders intact, they all look fine.
I’m thinking permissions issue, but all Joomla folder permissions are writable, same for all K2 folder permissions (as listed in K2 info)
Any ideas?
Do I need to UNINSTALL first? ( wouldn’t that delete all my blog data?)
From: Lefteris Kavadas notifications@github.com<mailto:notifications@github.com> Reply-To: joomlaworks/k2 reply@reply.github.com<mailto:reply@reply.github.com> Date: Wednesday, November 6, 2013 at 2:45 AM To: joomlaworks/k2 k2@noreply.github.com<mailto:k2@noreply.github.com> Cc: ". ." mike@rotech.ca<mailto:mike@rotech.ca> Subject: Re: [k2] upgrade K2 to 2.6.7 from 2.6.6 - glitch (#64)
Hi. Can you please install the development version and see if the issue remains? You can get it at http://getk2.org/assets/get
— Reply to this email directly or view it on GitHubhttps://github.com/joomlaworks/k2/issues/64#issuecomment-27862334.
fevangelou
commented
11 years ago Re-install Joomla please. Use the Joomla updater or Admin Tools to do so. Then try install K2 v2.6.7 on top of any other version you have now.
rotech1
commented
11 years ago Thanks Fotis!
I used Joomla updater to install latest Joomla (from 2.5.14 to to 2.5.15 ) . All shows OK ( permissions, db, etc) Even used Admin Tools “fix permissions”, to be on the safe side.
Then I installed standard K2 v2.6.7 – and got this:
Update: :Extension: Could not open http://getk2.org/update.xml
Invalid extension updateThank you for installing K2 by JoomlaWorks, the powerful content extension for Joomla! [http://dev1/media/k2/assets/images/system/K2_Logo_126x48_24.png] K2 Installation Status Extension Status
K2 Component Installed Module Client mod_k2_comments Site Not Installed mod_k2_content Site Not Installed mod_k2_tools Site Not Installed mod_k2_users Site Not Installed mod_k2_user Site Not Installed mod_k2_quickicons Administrator Installed mod_k2_stats Administrator Installed Plugin Group K2 Finder Not Installed K2 Search Not Installed K2 System Not Installed K2 User Not Installed K2category Josetta_ext Not Installed K2item Josetta_ext Not Installed
End result is that K2 info now reports that it is V2.6.7 – and also shows that all is well (!)
But I am getting the BOM problem (  at beginning of blog posts) Exactly as described earlier – and UTF-8 is scrambled in the comments, as also described earlier. No such issue on our live server running 2.6.6 …
Best regards, Michael
From: Fotis Evangelou notifications@github.com<mailto:notifications@github.com> Reply-To: joomlaworks/k2 reply@reply.github.com<mailto:reply@reply.github.com> Date: Wednesday, November 6, 2013 at 11:29 AM To: joomlaworks/k2 k2@noreply.github.com<mailto:k2@noreply.github.com> Cc: ". ." mike@rotech.ca<mailto:mike@rotech.ca> Subject: Re: [k2] upgrade K2 to 2.6.7 from 2.6.6 - glitch (#64)
Re-install Joomla please. Use the Joomla updater or Admin Tools to do so. Then try install K2 v2.6.7 on top of any other version you have now.
— Reply to this email directly or view it on GitHubhttps://github.com/joomlaworks/k2/issues/64#issuecomment-27905155.
When I upgraded on our development server to 2.6.7 it reported that all went OK - but on test-driving it, when an item was opened, the UTF-8 BOM was present at the top of the blog item!!
And various UTF-8 characters (apostrophes, quotation marks, etc) were scrambled in the comments. The identical data all displays perfectly in our 2.6.6. live server... Any possibility that one of the update's php files was edited in an editor that added BOM ?
(Note, this is K2 on Joomla 2.5)