ProsePoint incorrectly uncompressed by ALZip v6.7

Sorry, the problem comes up when I click on Channels Manager, not Content Manager.

Hi,

No, you shouldn't be getting an error message like that, and I don't think it's related to your use of XAMPP.

Unfortunately, I'm not quite sure what's causing it though.

That error message is implying a view is missing or has been renamed, but that view is an internal ProsePoint thing so you shouldn't have been able to mess around with it.

There's likely to be a new bugfix release of ProsePoint in the next couple of days. I'll see if I can add in some diagnostics or make the code a bit more robust.

BTW, if you absolutely must be able to run cron, comment out line 780 of .../profiles/prosepoint/modules/prosepoint/prosepoint_channel/pp_ch.module so the function pp_ch_cron() looks like:

function pp_ch_cron() {
// pp_ch_update_channel_editions();
}

Also, if you visit the Editions Manager or the Channels Manager (or both), do you get a similar error message?

Editions Manager has the same problem. Story Manager on the other hand is fine.

ProsePoint 0.06 has been released. It contains some diagnostics and code to handle this error better. Can you give that a try? Thank you.

Do I need to upgrade from 0.05 or should I just reinstall afresh or ....?

Either is fine.

Upgrading is a little bit more work than re-installing, but it's up to you. See http://www.prosepoint.org/docs/upgrading-prosepoint.html.

Of course, if you reinstall, you lose all your data.

I did a fresh install and now just get a blank white page when I try to access either the Channels Manager or Edition Manager. Also, on the front page I am now getting:

ProsePoint error: Missing view channel_editions_archive

> ProsePoint error: Missing view channel_editions_archive

This error message are added in 0.06, rather than causing a php Fatal Error message.

1. Blank white page
You shouldn't get a blank page when vising the Channels or Edition Manager though. Can you check your PHP / web server logs to see if there are any php error messages in there?

2. ProsePoint error: Missing view channel_editions_archive
This is a fairly drastic error message. It's complaining that a view (which is used internally) is missing.

There should be a file .../profiles/prosepoint/modules/prosepoint/prosepoint_channel/views/channel_editions_archive.view. Can you tell me the length (in bytes) of this file on your system?

1. I'm not sure my php is set up to record an error log. I'm trying to figure out how to set that up, but slow going.
2. I don't appear to have that file in my folder. Closest thing I have is channel_editions_arc0000644 which is 4,670 bytes.

2. That's probably the problem. That file wasn't correctly uncompressed.

Can you give me a details listing of the following directories (ie. "dir" from the command prompt, if I remember my dos correctly)?

.../profiles/prosepoint/modules/prosepoint/views
.../profiles/prosepoint/modules/prosepoint/prosepoint_channel/views
.../profiles/prosepoint/modules/prosepoint/prosepoint_editor/views

I want to see a list of filenames and file sizes.

Also, what software are you using to uncompress the ProsePoint tar.gz file?

I'm using ALZip v6.7

.../profiles/prosepoint/modules/prosepoint/views

pp.views 1032 bytes
pp.views_default 537 bytes
pp_views_handler_field_story_edition_re0000644 2051 bytes
story_view.view 10457 bytes

.../profiles/prosepoint/modules/prosepoint/prosepoint_channel/views

channel_editions_arc0000644 4670 bytes
channel_editions_fut0000644 5281 bytes
channel_editions_lis0000644 5116 bytes
channel_stories.view0000644 5042 bytes
editions_view.view 7405 bytes
pp_ch.views.inc 1624 bytes
pp_ch.views_default.0000644 792 bytes
pp_ch_views_handler_0000644 603 bytes

I'm sensing a theme here with the 0000644 files. Should I try reinstalling using a different compression program?

Yes, please try using a different uncompressor.

Many of those files have been corrupted. Below, I have listed what you should be seeing (listing from my linux box).

Let me know how you go.

(So, in retrospect, it wasn't related to Windows/XAMPP, but it was related to Windows... sort of)

prosepoint_channel/views:
total 68
-rw-r--r-- 1 beng beng 4670 2008-10-23 07:57 channel_editions_archive.view
-rw-r--r-- 1 beng beng 5281 2008-10-23 07:57 channel_editions_future.view
-rw-r--r-- 1 beng beng 5116 2008-10-23 07:57 channel_editions_list.view
-rw-r--r-- 1 beng beng 4265 2008-10-23 07:57 channels_list.view
-rw-r--r-- 1 beng beng 5042 2008-10-23 07:57 channel_stories.view
-rw-r--r-- 1 beng beng 7405 2008-10-23 07:57 editions_view.view
-rw-r--r-- 1 beng beng 792 2008-10-23 07:57 pp_ch.views_default.inc
-rw-r--r-- 1 beng beng 1226 2008-10-23 08:12 pp_ch_views_handler_field_edition_state.inc
-rw-r--r-- 1 beng beng 397 2008-10-23 07:57 pp_ch_views_handler_field_next_eid.inc
-rw-r--r-- 1 beng beng 603 2008-10-23 07:57 pp_ch_views_handler_field_next_schedule.inc
-rw-r--r-- 1 beng beng 1624 2008-10-23 07:57 pp_ch.views.inc

prosepoint_editor/views:
total 24
-rw-r--r-- 1 beng beng 2999 2008-10-23 07:57 images_list.view
-rw-r--r-- 1 beng beng 2994 2008-10-23 07:57 media_list.view
-rw-r--r-- 1 beng beng 584 2008-10-23 07:57 pp_ed.views_default.inc
-rw-r--r-- 1 beng beng 464 2008-10-23 07:57 pp_ed_views_handler_field_node.inc
-rw-r--r-- 1 beng beng 879 2008-10-23 07:57 pp_ed_views_handler_thumbnail.inc
-rw-r--r-- 1 beng beng 1522 2008-10-23 07:57 pp_ed.views.inc

views:
total 24
-rw-r--r-- 1 beng beng 537 2008-10-23 07:57 pp.views_default.inc
-rw-r--r-- 1 beng beng 2051 2008-10-23 07:57 pp_views_handler_field_story_edition_ref_multiple.inc
-rw-r--r-- 1 beng beng 1032 2008-10-23 07:57 pp.views.inc
-rw-r--r-- 1 beng beng 10457 2008-10-23 07:57 story_view.view

Sorry for the delay. Reinstalled with a new compression agent and everything works great now. Very sorry for all the confusion. I (naively) never realized a compression agent could arbitrarily change file names like that.

Now that everything is working, I'm going to go ahead and install ProsePoint for a site that I'm building. I think the url is going to be hydrajournal.com. Thank you for all the help thus far.

You're welcome. I'm just glad we got it sorted out, and it wasn't a problem with ProsePoint.

> I (naively) never realized a compression agent could arbitrarily change file names like that.

They're not supposed to. It's definitely their bug :)