LoudBlog - Podcasting-Software for PHP - Forum

Hello Gerrit,

Upgrade script seemed to work perfectly, no errors anywhere that I have found.

I suppose the most logical question concerning iTunes Categories and iTunes Cover Art would be:

Would it not make better sense to have these on a file-by-file bases rather than on a one-for-all?

I suppose I had more expected ID3 tags to be updated, rather than the rss.

When a new podcast file is uploaded I would tend to think that it should be able to have a specific Cover Art assigned (uploaded and attached) to it. Perhaps even putting this into the "edit ID3 tags" page would be an acceptable place for it.

I'll continue to test and report back any further comments.

After updating:

On the podcast-feed information in the backend-settings there is displayed the following:

<br /><b>Notice</b>:  Undefined index:  itunes_author in <b>/.../loudblog/loudblog/inc/backend_settings.php</b> on line <b>142</b><br />

in the first three fields.

In the "explicit lyrics" field is displayed the following:

"Notice: Undefined index: itunes_explicit in /.../loudblog/loudblog/inc/backend_settings.php on line 206"

It won't change even if I choose a setting and click on "Save".

In iTunes categories there is displayed:

"Notice: undefined"

In language it is the same.


What can be the problem?


Furthermore after running the update-file a file-not-found message opens up. Would be better to display a update-done-page ...


One more question: Is it normal, that when you click on "Play" in the flash-box and click stop after a few seconds, the file downloads completely?


Greetz,

André

Hi Gerrit,

I have found the problem. It is in the original-zip-packing of the files.
You have packed the updateXX-XX.php's into the /.../loudblog-folder, so when starting them from that place, the update fails or at least is not made completely - resulting in my problems.
After moving them manually one level up into the top loudblog-folder on the server, the installation worked perfectly and I got a success-message. All the mentioned problems are gone now, as far as I can see.
So you should encode a new zip-File with the updateXX-XX.php's at the right place in the top-level directory where the install.php is ...

I know, these things usually belong to the bugs and problems-forum. Maybe you can move them ...?


Best regards,

André

Last edited by planetgroove (Jul 3rd 2005 08:01)

@planetgroove: You don't have to move the update-files, you have to simply write the "/loudblog/" path into your browser, when opening those files.

Anyway, I put the update-files into the loudblog-folder, because I don't want that the user would have to change or copy anything to the root-directory of his LB-installation. All update changes should be inside the "loudblog" folder.

So it's not a bug, it's a feature! Updating from 0.1 to 0.2 went the same way and it was no big deal for most of the users.

I found one mistake in the update-files:

<link rel="stylesheet" type="text/css" href="loudblog/backend/screen.css" />

The stylesheet is not linked correctly.

But as far as I can say, the update process cannot work when you start it from the root folder of your installation. Look at that:

//get database connection values
include "custom/config.php";

It tries to get the database connection values. If you transfer the update-file to the root directory the script won't be able to find those values, because they are linkes relatively and the path is wrong. The update script cannot change anything at all.

Seems like there is some magic going on on your server. I can’t explain. But finally everything works fine with your installation?

@ Gerrit:

Yes it works now. I hope the next update will do without moving any file ...

:-)

André