Sandbox

Moderator note :

Post split, information an fix for media manager problem in Joomla 1.0.4 can be found in this thread :
http://forum.joomla.org/index.php/topic,20033.0.html

brad wrote:Have you got a link to your site? This is not something I have seen on any sites that I have upgraded.. or even on the official Joomla sites.

The "overLIB 4.10 is required for the HideForm plugin" is displaying in the admin area on some sites. Not all.

mediamagnate wrote:

brad wrote:Have you got a link to your site? This is not something I have seen on any sites that I have upgraded.. or even on the official Joomla sites.

The "overLIB 4.10 is required for the HideForm plugin" is displaying in the admin area on some sites. Not all.

Don't often reply to myself but the fix for this may be as simple as a cache issue.

Before thinking you've got an indefinite issue, make sure you've cleared all your caches in the admin by going to SYSTEM > CLEAN ALL CACHES.

Fixed my problem.

Coder-Pete.. good find..

Everything upgraded very nicely, did the quick fix for the media manager and now I'm set. Great job Joomla team !

Is there any reason why there are what appears to be two empty directories in the 1.0.3 to 1.0.4 package? (haven't checked the others)

installation
installation/sql

Can I remove these?

Why did this update go through and change ownership (user and group) to 1000 for many of the directories?

Im getting an error when adding and editing content. If I click the save button nothing happens. Checking the firefox javascrip console I get the following:

Error: form.medialist has no properties
Source File: http://rebelplanetcreations.com/adminis ... index2.php
Line: 717

Any Ideas?

Ok i fixed it. I guess I was on 1.0.2 not 1.0.3 the patch i applied.


Guess it helps if you apply the right patch

Anyone seeing this on the control panel? The text isn't aligned correctly.

Jestre wrote:Why did this update go through and change ownership (user and group) to 1000 for many of the directories?

That would not have had anything to do with the patch. How did you overwrite files? ftp?

kai920 wrote:Anyone seeing this on the control panel? The text isn't aligned correctly.

Yup, I saw this until I did a "refresh" in my browser to pull the latest CSS file.

brad wrote:Have you got a link to your site? This is not something I have seen on any sites that I have upgraded.. or even on the official Joomla sites.

It's interesting to me that when I apply the patch to a 1.0.3 installation created by Fantastico, I get this error. But if I install Joomla 1.0.3 manually, and then apply the patch, or if I just install 1.0.4 full package manually, then no such error is created. The Fantastico 1.0.3 script installation process could be the cause of these problems. I wonder how many of the reports are from people who are attempting to patch a Fantastico-installed Joomla?

MikeFossati wrote:

infograf768 wrote:ISO has been reset to 8559-1 instead of utf-8.

As this is causing some problems on my site, I wonder if there is a simple way to fix it? Instead of "..." I see now "…" (check my site for an example: http://www.spiritofhouse.com/).

Thanks for your help,
Mike

If I change this back to "utf-8" in the "englishl.php" file, does this break anything from working?

Mike

rhuk wrote:

kai920 wrote:Anyone seeing this on the control panel? The text isn't aligned correctly.

Yup, I saw this until I did a "refresh" in my browser to pull the latest CSS file.

*poof*  like magic!

mediamagnate wrote:

mediamagnate wrote:

brad wrote:Have you got a link to your site? This is not something I have seen on any sites that I have upgraded.. or even on the official Joomla sites.

The "overLIB 4.10 is required for the HideForm plugin" is displaying in the admin area on some sites. Not all.

Don't often reply to myself but the fix for this may be as simple as a cache issue.

Before thinking you've got an indefinite issue, make sure you've cleared all your caches in the admin by going to SYSTEM > CLEAN ALL CACHES.

Fixed my problem.

Crazy as I am, I tried to find what causes the overLiB 4.0 error, I dont know for sure but when I restore the pagination.php files then the error goes away, this includes the files from; mambots/content and /includes all files have something to do with pagination...
When I restore the 1.03 files its gone...

Will there be a zip file? Thanks!

If you can't open the tar.gz-file, you can download and install 7-zip from http://www.sourceforge.net. This is a file packing program which can untar the compressed files.

Thanks much - I found it and it worked great. Appreciate the help for this newbie!

upgraded all of my sites (8 i think) and no problems as of yet.  Great Work!!

brad wrote:

Jestre wrote:Why did this update go through and change ownership (user and group) to 1000 for many of the directories?

That would not have had anything to do with the patch. How did you overwrite files? ftp?

Since some of the files are owned by apache, I did basically the following:

cd $joomla_dir

sudo tar zxf /path/to/Joom_1.0.3-blah-blah.tar.gz

After the upgrade I have a few problems with displaying the content. I have a few content items that I generated in another application and copied the whole html into "No WSISWYG editor". Everything was fine with Joomla! 1.0.3 but now I get " " all over the place :-(

It seems that " " is not parsed correctly and is shown as plain text. Has this anything to do with the charset? Please help because know half of my site looks very ugly..

Thanks, Fabster

Jinx wrote:Moderator note :

Post split, information an fix for media manager problem in Joomla 1.0.4 can be found in this thread :
http://forum.joomla.org/index.php/topic,20033.0.html

Due to this problem, Are you going to release a patched version 1.0.4?

Heh - you know you want to!
1.0.4.1...

Gary

dyrer wrote:

Jinx wrote:Moderator note :

Post split, information an fix for media manager problem in Joomla 1.0.4 can be found in this thread :
http://forum.joomla.org/index.php/topic,20033.0.html

Due to this problem, Are you going to release a patched version 1.0.4?

Not forecasted, info has been spread:
http://forum.joomla.org/index.php/topic ... #msg120976
You may find a link there to get the whole file content.

For those of you using joomlahacks.com SMF Integration with the login module you will have 1 issue after the upgrade.  Your login section will be a bit goofy....

Here is the fix :

http://www.joomlahacks.com/component/op ... en#msg4196

I didn't find the fix and in no way shape or form have anything to do with any of this... I'm just a peon handing over a piece of info you other guys might be checking here for.

Cowboy... and the guys who answered that post from someone else... thanks... you are doing a great job. (as is the Joomla dev team... obviously)

kai920 wrote:Anyone seeing this on the control panel? The text isn't aligned correctly.

Yeah on one of my sites it looks just like that, I've upgrade about a dozen hosted and of course my site is the one with funky weirdness.

*EDIT*
Then I read rhuk's post and began to feel like idiot.

infograf768 wrote:ISO has been reset to 8559-1 instead of utf-8.

Changing from "8859-1" to utf-8 in Joomla 1.0.2 , and now changing this back from "utf-8" to "8859-1" in Joomla 1.0.4 in the "english.php" file without warnings or database re-encodings does break not only the appearance but also the databases themselves (also English ones, see special characters) !

From the little I understood, when you change encoding in the front, you need to resync/update the database, to avoid not only loosing appearance of non-ASCII characters, but also to put the database in a mixed character encoding state.

I initially understood the utf-8 was for Joomla 1.1 with a proper database upgrade mechanism on CMS upgrade. But "playing" like that with character sets doesn't seem really "safe" for our databases integrity.

Admins should at least be warned and given instructions on how to re-encode their database safely.

Are we trading in safety for security ?
I hope I'm missing something... ?

or what's the plan now ?

10x guys for your work!

Beat,

We indeed messed up with the UTF-8 work. We tried a move to UTF-8 in 1.0.3 and then decided to only do it in 1.1. Changes were reveryed but the language iso setting was forgotten. We fixed this in 1.0.4 and forgot about the possible consequences. U are right that we should have informed our users about this change. Our apologies !

U can do two things are u change the iso settings in the english langauge file back to UTF-8 or u resave your content items. We are sticking with ISO-8859-1 for the 1.0 series. In your case it might be better to change them back to UTF-8.