PDA

View Full Version : DFP2 - can't see progress bar


gwh362692
06-01-2009, 10:03 AM
Hi everyone,

I've just tested out digital file pro 2. Everything works as expected except that no progress bar appears when uploading files.

Anyone know why this is happening?

Ray Borduin
06-01-2009, 10:20 AM
Do you have a url where I can view the page?

gwh362692
06-01-2009, 10:23 AM
Sure - it's:

http://energetics.officelinkonline.com.au/

Ray Borduin
06-01-2009, 10:32 AM
It looks like you are missing all of the necessary javascript files and references on that page. Maybe try applying the progress indicator to another page and use that as a reference for what missing .js files you need to add to the current one.

gwh362692
06-01-2009, 10:37 AM
It looks like you are missing all of the necessary javascript files and references on that page. Maybe try applying the progress indicator to another page and use that as a reference for what missing .js files you need to add to the current one.

I just tried it again on another page and no javascript files and references appeared so I can't apply them to the original page. Do you know what's happening?

Ray Borduin
06-01-2009, 10:40 AM
No I don't. It appears to be some sort of bug, but I can't imagine the cause. Are you using a template or a really old version of DW? Anything strange about your folder names or OS?

gwh362692
06-01-2009, 10:43 AM
No I don't. It appears to be some sort of bug, but I can't imagine the cause. Are you using a template or a really old version of DW? Anything strange about your folder names or OS?

No template and I'm using DWCS4 and mac os 10.5.7

Only thing I can think of is that when I tried to remove the old version of DFP it took about 5 minutes to remove. Could this be the problem and should I try to remove and reinstall the new extension?

Ray Borduin
06-01-2009, 11:14 AM
I don't think so... but I guess it is possible. Try fully removing and reinstalling the extension. That is my best guess. I forward this to someone at the office with your OS to see if they can reproduce it.

gwh362692
06-01-2009, 12:19 PM
Ok - I'll give it a try

Dave Buchholz
06-02-2009, 04:00 AM
FWIW I have exactly the same issue, OSX 10.5.7 / CS4. I will submit a support incident with a test page.

Ray Borduin
06-02-2009, 05:57 AM
Thank you. We test on that platform so it is odd to run into the error. Did you do a complete uninstall before installing the new DFP 2, or did you install over it in extension manager.

Lately most of our issues have been caused by extension manager in some way, that is why I tend to look for the problem there first these days.

Dave Buchholz
06-02-2009, 06:12 AM
Ray,

Yes I always uninstall previous versions before installing the current version and delete the macfilecache before relaunching DW

Ray Borduin
06-02-2009, 06:38 AM
Thanks for posting a support incident. My only guess is that the platform somehow escaped adequate testing. I don't have a MAC so I am unable to try to reproduce here but I got word that we are already looking into it when I reported this post yesterday.

Dave Buchholz
06-03-2009, 12:50 AM
For Info:

Looking in Macintosh HD -> myusername -> Library -> Application Support -> Adobe -> Dreamweaver CS4 -> en_US -> Configuration -> Shared -> WebAssist ->DigitalFilePro ->Helpers I can see a file called jquery-blockui-formprocessing.js which is obviously the js file that should be linked to the page but when adding the Progress Bar this js file is not put into my DFP folder in the site nor is it linked to the page.

Ray Borduin
06-03-2009, 06:31 AM
It must be specific to that platform. We will have to fix the problem and provide an update. Your analysis of the problem is entirely accurate. It must not be calculating either the source or destination path properly when copying the files on that platform.

I got word that we were looking into the problem, but some of our engineering resources had to be diverted to support this week since our head of support is on vacation. I'll make sure the program manager in charge of dot releases is aware of the severity of this problem. Thank you for the further clarification. You can obviously copy and add a reference to this file manually in the meantime to get the application to work properly.

troyd
07-23-2009, 11:39 AM
Was this issue ever resolved? My experience is similar so far, but with one exception, the jquery-blockui-formprocessing.js file IS being put in the DFP2 folder and it is uploaded to the server along with the WA_DigitalFilePro folder. Is this the correct .js file? Doesn't the blockui simply block the user from doing anything until the form is processed? Should there be another external file?
There is a script on the page. Along with a div and some inline styling it looks like.

<div id="form1_ProgressMessageWrapper" class="blockUIOverlay" style="display:none;">
<script type="text/javascript">
WADFP_SetProgressToForm('form1', 'form1_ProgressMessageWrapper', WADFP_Theme_Options['BigSpin:Pacifica']);
</script>
<div id="form1_ProgressMessage" >
<p style="margin:10px; padding:5px;" ><img src="/WA_DigitalFilePro/images/pacifica-largespin.gif" alt="" title="" style="vertical-align:middle;" />&nbsp;&nbsp;Please wait</p>
</div>

I have highlighted the progress bar behavior and clicked edit to make sure it follows through with any changes. Everything looks good but no progress bar shows up when I upload a file that takes several seconds.

This could be user error. But I have read and re read the GSG PDF and I don't see where I am missing anything. Unless there is suppose to be a CSS file, which there isn't.

You don't see the message either. Do I need to apply a style to the div containing the message and image? Is it there, but collapsed?

I am using the beta version. I did a full uninstall before the install.

Any thoughts here? What should I try next?

Thanks,
Troy

Ray Borduin
07-23-2009, 11:45 AM
This should have been resolved in the most recent version.

troyd
07-23-2009, 12:17 PM
I agree. (tongue in cheek).

Should I just submit a ticket?

Troy

Ray Borduin
07-23-2009, 01:13 PM
Yes, please submit a ticket and somebody can work to debug and resolve this issue.