Problems problems problems...

8/22/2012 6:08 am | #1 mrs

You can tell I've just started to use the new extensions in earnest... you're getting a lot of questions from me! ;o)

I am finding a few problems with pages that I am creating with Data Bridge's Data Assist!

I can create the pages fine, and upon basic inspection they seem to be working fine. I apply my template to the pages and that all seems fine until I realise that the access manager rule applied to the template has been deleted. All the pages I now have with this template are not protected! So, what's going wrong here? Why is the PHP that I have added to the template been deleted when I apply the template to a page?

I've created an update page which has a file field in it. The insert page works fine, but the update page is having issues in a few ways. Firstly, I have stupidly applied spry validation to the file field so that it is required to be completed on insert. The obvious to me now problem is that if I wish to update the record simply by changing associated text, the file field has got spry validation applied to it and won't submit the page... I might not want to update this field, so how do I get rid of validation on the update page? I've tried, but the page won't submit. Perhaps a future version of DA will enable us to select if we want required fields to be different between insert and update pages.

Another issue with the file field on the update page is that the DA wizard has created the upload process to overwrite the existing same name file, whereas I want it to increment the file name. I open the Upload Files server behaviour to edit it, click on finish, but the finish button of the wizard doesn't work. It won't go away and apply the changes I have made. Is this a bug, or am I neglecting to complete something in the wizard? I'm sure I'm not.

One more issue with that I have come across is with respect to making a menu in DA that is fed by a table in the database. I have my DB table tbl_menu, and I have asked DA to pull data from that, but when I check the update page I am finding it's not selecting the correct menu option... all options are there, just not selected based on what is stored in the DB record. Upon inspecting the code I found that the wizard has created two recordsets (one for the record I am editing, and one for the menu I'm pulling values/options from). The wizard has asked for content from the wrong recordset. Again, I've edited this, but why is it set wrong? Is it something I've done?

Thanks.

Mat

8/22/2012 8:39 am | #2 msummers194171

> So, what's going wrong here? Why is the PHP that I have added to the template been deleted when I apply the template to a page?

You may be getting caught in the fact that the region above <html> is regarded as an EDITABLE REGION by the template engine. In that case, editable region content is not propagated to child pages.

I have been doing exactly the same thing, but in reverse sortof. My approach is to create the DB pages, then create a NEW child page from the template, and copy/paste content from the existing DB pages into the new child pages. That way I can make sure that all of the important stuff gets into the right place. Of course this presupposes that you know what is the important stuff to copy and where to copy it!

We would probably have to see your page to tell you what to do about the file field validation issue - but generally, you'd click in the field (in Design view) then click on the Spry tab that appears on the screen (the CYAN one), and finally select the highlighted tag on the tag selector before clicking on the delete key. That gets rid of the Spry stuff around the file field - you'd still have to remove the corresponding Spry javascript variable definition at the bottom of the page's code to complete the job.

We'd definitely need to see your code for the other two issues.

8/22/2012 12:00 pm | #3 Jason ByrnesWebAssist

The issue with the template is really just a limitation to the way templates work.

When using templates, you can either apply all your server behaviors to the template, or you can apply server behaviors to the individual pages.

Obviously, applying the server behaviors to the individual templates is more desirable.

This is where framework builder and themes comes in handy. Using framework builder themes themes allows you to over come this inherent limitation to dreamweaver templates.

In the Videos tab of the Design Extender support page there is a tutorial "How to convert your site from DWT-dependent to theme-based" that talks about converting templates to themes:
design-extender/

For the file field validation issue, there is probably Spry Validation and Server Side validation applied, you will need to remove the required validation from both.

for the issue you are having editing the upload behavior, see this post:
showpost.php?p=133714&postcount=4

Technical Support Forums

Free, outstanding support from WebAssist and your colleagues

Problems problems problems...

8/22/2012 6:08 am | #1 mrs