WDL file not copying and renaming with project template

[Cole64]

Hello,

I have created a project template which I use for creating all my new projects and have found that the .WDL file is not copied over (and renamed suitably). Is there a way to make sure that this happens or do I have to manually copy and rename this file?

Thanks

Colin

[rhesusminus]

Hi Colin.

What is your wdl-file named? And you are of course using the copy project tool?

[jseefdrumr · Accepted solution]

What version are you on?

I do the same thing as you, and I don't have this issue. I just started a project this morning from my template project, and it brought the wdl file. I'm using ACADE 2017.

As Trond hinted, it matters what process you're using to copy the project. When you use the ACADE tool Copy Project, the fourth step is a dialog that asks you which files to copy, and how they should be renamed. The wdl file is one of these. Note that every one of these is greyed out unless it is available to be copied. So if you don't have a wdl file in the project directory, you'll see it in the list but you won't be able to select it. Regardless, if you're not seeing this dialog you aren't using the workflow that is intended for this purpose.

As a side note, the wdl file name shouldn't change. I can confirm that the copy is created, however, because in my template project the file name is in caps, but after the command, the copy in my new project was in lower case. I'm pretty sure that this is all how it's supposed to work.

Jim

[Cole64]

Hi Guys,

Sorry for the late response, I have been of work. I have not been using the 'copy project' function in the Project tab, but when I do it does copy the .wdl file across with lowercase letters and all the descriptions come through as expected. I was using the Create new project icon in the Project Manager panel which has the 'Copy Settings from Project File' option, which I would expect to have the same functionality as the 'Copy Project' function.

Well I know how to achieve what I want so I guess this is solved, thanks guys.

[Anonymous]

I have been using the copy project command from the ACADE ribbon since ACADE 2010.  The WDL file has always changed to match the WDW and WDP files exactly as the WDP file was first set up, through the copy project process.

This has worked for me, flawlessly, through ACADE 2010, 2011, 2012, 2013, 2015, 2017.

However, for some strange and unknown reason, the WDL file is now being copied to the new project with the previous project text.

The offending project was crippled by a hack and slash artist, and later "fixed".

Of course, this is the project they want to use for training purposes  and as a standard template.

If I copy/paste the WDP text to the WDL file, the "Descriptions..." lines change to match the WDL file.

Everything is great and wonderful until the next copy project.

Example:

The three files should look like this:

project copy.wdp

project copy.wdw

project copy_wdtitle.wdl

But after the copy project, they look like this:

project copy.wdp

project copy.wdw

previous project text_wdtitle.wdl

("project copy" and "previous project text" are not what we actually use for file names)

Any ideas on why the WDL file won't change to match the WDP file?

I am very good with ACADE, but this is a new one for me, I haven't seen this before in my drawing sets.

Any Autodesk folks out there want to take a stab at this?

[dougmcalexander]

It sounds like something may be corrupt, possibly in both the wdp file and the _wdtitle.wdl file.  My suggestion is to create a fresh _wdtitle.wdl file and not copy and paste from a wdp file.  In fact, I don't advise anyone to open the wdlp file at all.  Let the software manage it.  The are spaces and symbols in the wdp file that could accidentally get deleted and lead to problems. 

In fact, I would suggest that you even create a new wdp file, by creating a fresh new project. 

1. Create a new project

2. Copy the drawings and wdw file from your offending project into the new project's folder. (Do not copy the wdp file or the _wdtitle.wdl file.)  

3. Rename the .wdw file to match the new project name or name it default.wdw.

4. Add the drawings to this new project. 

5. Use the Settings Compare utility to make the project properties match the drawing properties.  (This is the method I use when clients send me their drawings but forget to send the wdp file.)

6. Create a _wdtitle.wdl file using Notepad or WordPad.

Hopefully this fresh start will allow your project to copy properly in the future,.

[Anonymous]

Thanks Doug for the reply, I have thought of doing what you suggested as a last resort, I was hoping it was just a setting or something simple.

[dougmcalexander]

Yes, I know that isn't a first choice, but I would try that before resorting to more drastic efforts. 

It does provide the advantage of refreshing your memory on how to do certain things that you normally set and forget.  For me, the reason I am so fast and efficient at helping my clients create their template, set up customization, set up network sharing, configure custom report generators, and customize the menus, both ribbon and icon menus, is because I do it frequently.  The average customer should only need to set things up once and done.  So many administrative tasks are hard to remember because you do them once and you're done.  Each time I get a new release, I manually add all of my ribbon menu customization just to keep me current on how to use the CUI editor..

[Icemanau]

Unless you are using different Line Descriptions for the Title Block Descriptions for each project, you would only need one wdl file.

Make a backup copy of your wdl file and rename it to default_wdtitle.wdl and place it in the first directory of your support file tree.

ACADE will first of all, look for the PROJECT_wdtitle.wdl file in the project directory.

If ACADE can't find a PROJECT_wdtitle.wdl file, it will check the support directorys for the default_wdtitle.wdl file and will use it if it finds it.

This negates the need to gave copy the file when creating or copying a new project.

It also has the advantage of less room taken on the drive and if it's on a network location, being available for for all users with all users having the exact same descriptions in use. Plus if you have to make a change, it's only one file and will affect all projects.

Personally, I currently have two WDL files.

The first one is for our companies standard title block and is named default_wdtitle.wdl and saved in the search path for support files.

The second WDL file is for one specific client who demands we use their title block with a totally different layout and attributes.

This WDL file gets copied to each new project for that client and that client only. As they are only about 10% of our business, there is no need to set their WDL file as the default.

Regards Brad

[Anonymous]

Good information, but you’re not telling me anything I don't already know, the original question was about the WDL file not changing its name to match the WDP file.  I took a known working WDP file and replaced the WDP file in my project and did a copy project, it renamed the WDL file to match it.

That's how it is supposed to work.

So, something was corrupt with the WDP file.