Phoca download 1.3.4 files dont show up in frontend

[bowie]

I have installed PD 1.3.4. Created section and category (PUBLIC access). Uploaded a file (pdf) in the backend, authorized it and published it.
When accessing the file in the menu (section layout) the files do NOT show up? My categories and sections shows up fine, but NOT my files??
Please help

[Jan]

Hi, check all the parameters of the file (if it is for public, etc)

[mik007]

Hi!

I have the same problem. Ive uploaded 4 files for testing. Ive transfered them throug ftp. All files shows up in frontend, EXCEPT one zip file. The zip file just do not want to show up. Ive aproved and published the file. Ive also tried to upload through bakend. Ive tryed to chmod the file to 777. The file is in tha same folder with the files that shows up...

[bowie]

Hi, i too changed the file to 777 - and to no help

[mik007]

Hmmm... suddenly the file appeared... WHY? I havent done anything special...

[marben]

Files - check item "PHOCADOWNLOAD_START_PUBLISHING:"

[emal011]

I had the same problem and I think there is a bug in this new feature "publishing".
When you press the New Button to add a new file then the field PHOCADOWNLOAD_START_PUBLISHING is filled out with the current time and date. After saving the File this field changed into another time (current time +2hours). The field DATE which is empty before saving is now filled out with the current time -2hours.
Why do the fields filled out themselves???

Is it possible to deactivate this function?

Thanks!!
Limbi

Yep!

I have the same problem... I already try everithing, but nothing works, it always say Published Pending--- I already make it by administrator panel, but nothing.. And like Limbi say, if I try to modificate the "Start Publishing" date, it come +2 or -2.. but even after that time, nothing happend...

[Jan]

Hi, this will be solved in 1.3.5

[TopCop]

Jan,
I have installed Ver 1.3.5 but this problem still exists.


TopCop

[marben]

To TopCop > Download and install file again - this version is ok. Your version 1.3.5 is maybe wrong (the first install file here has been wrong).