Approval templates don't fire when updating document

I'm running trials in my test database and it appears that approval templates only work on new added documents? SAP Business One version 8.82 I am testing a query that calculates certain criteria against the business partner's credit limit. If there is a deviation I want the approval process to start.
Everything works fine when I add a new sales order with a doctotal that deviates from my credit limit logic. Approvals fire off and the user has to wait for the manager to approve. However if I add a sales order with zero value and then go back in and update the pricing later the approval never triggers. So users are just able to go around approvals by adding blank documents first and then updating them however they see fit.
Am I doing something wrong or is this just how SAP B1 approvals function? Do approval templates have any impact on updated documents?

Do TN's throw the red bar erros at the bottom of the client's GUI? The ones that look like this...
I'm looking through the following documentation...
http://scn.sap.com/docs/DOC-7034
and I can't seem to confirm what returning @error = 1 will actually cause.

Similar Messages

DRQ# Approval Process Does Not Fire on Update of Document

Hi,
If a purchase order is added for a value which does not require approval, then later the actual price of the order is known and is a value which requires approval, the user is able to update the purchase order without an approval procedure being triggered.
Note #925685 states that approvals will not trigger on update, however this means a user can modify documents to a value which should require an approval process.
Lianne

Hi Lianne and Davis,
I was wondering if you already found a solution for this problem.
Unfortunately I did not found your post about the approval process.
( Re: 925685 - Approval process is not triggered after documents are added )
Do you know if this is solved within 8.81 or did you find another solution?
Kind regards,
Marcel Kieboom

Slow respon when update Document Numbering

Hi Expert,
We have 7 branch and 4 different type of sales document. and we change our document numbering every month.
We have use SAP Business One for a year. So, we have large number of document numbering.
when we update and add new row in document numbering, we get slow respon. It can about 30 minutes every update.
how can we make it faster?
*we use 8.82 PL:08 version.
Regards,
Triadi Bagus

Hi Triadi,
Try to update Document Numbering when no user are logged on data or Ask your users to not to post any transaction during the period when you are updating Document Numbering.
This problem arise because when user are punching transactions on database as Internal Document No Changes every time a transaction is punched on Database.
This May be the reason.
Hope this help!!
Regards,
Sudhir

All DocumentSet derived ContentTypes' EventHandlers fires when uploading document

I have made a custom "base" content type based on the Document Set content type. On this content type I attach 6 EventHandlers:
<ContentType ID="0x0120D5200088cd8a49c45a45dbb0b808d0934cd901"
Name="My Magical Base Document Set"
Description="My Base Document Set"
Group="Magical Content Types"
ProgId="SharePoint.DocumentSet"
PushDownChangedResourceFilesOnly="TRUE"
Version="0">
<FieldRefs />
<Folder TargetName="_cts/MyDocSetCustom" />
<XmlDocuments>
<XmlDocument NamespaceURI="http://schemas.microsoft.com/sharepoint/events">
<Receivers xmlns:spe="http://schemas.microsoft.com/sharepoint/events">
<Receiver>
<Name>MagicalBaseDocumentEventHandlerItemAdding</Name>
<Type>1</Type>
<Assembly>$SharePoint.Project.AssemblyFullName$</Assembly>
<Class>MyMagicalProject.EventHandlers.MagicalBaseDocumentEventHandler</Class>
<SequenceNumber>50</SequenceNumber>
</Receiver>
<Receiver>
<Name>MagicalBaseDocumentEventHandlerItemUpdating</Name>
<Type>2</Type>
<Assembly>$SharePoint.Project.AssemblyFullName$</Assembly>
<Class>MyMagicalProject.EventHandlers.MagicalBaseDocumentEventHandler</Class>
<SequenceNumber>50</SequenceNumber>
</Receiver>
<Receiver>
<Name>MagicalBaseDocumentEventHandlerItemDeleting</Name>
<Type>3</Type>
<Assembly>$SharePoint.Project.AssemblyFullName$</Assembly>
<Class>MyMagicalProject.EventHandlers.MagicalBaseDocumentEventHandler</Class>
<SequenceNumber>50</SequenceNumber>
</Receiver>
<Receiver>
<Name>MagicalBaseDocumentEventHandlerItemAdded</Name>
<Type>10001</Type>
<Assembly>$SharePoint.Project.AssemblyFullName$</Assembly>
<Class>MyMagicalProject.EventHandlers.MagicalBaseDocumentEventHandler</Class>
<SequenceNumber>50</SequenceNumber>
</Receiver>
<Receiver>
<Name>MagicalBaseDocumentEventHandlerItemUpdated</Name>
<Type>10002</Type>
<Assembly>$SharePoint.Project.AssemblyFullName$</Assembly>
<Class>MyMagicalProject.EventHandlers.MagicalBaseDocumentEventHandler</Class>
<SequenceNumber>50</SequenceNumber>
</Receiver>
<Receiver>
<Name>MagicalBaseDocumentEventHandlerItemDeleted</Name>
<Type>10003</Type>
<Assembly>$SharePoint.Project.AssemblyFullName$</Assembly>
<Class>MyMagicalProject.EventHandlers.MagicalBaseDocumentEventHandler</Class>
<SequenceNumber>50</SequenceNumber>
</Receiver>
</Receivers>
</XmlDocument>
</XmlDocuments>
</ContentType>
I then create 24 new content types based off of the above content type and I bind them to a document library.
After deployment, when the content types are all created and the library is created and have all the content types binded, I create a new document set in this library. I then try to add a new item (document).
This is where the interesting thing happens. When I add a Word or Excel document none of the EventHandlers are fired. But when I add a PDF, TXT, or XML document then the ItemAdding EventHandler is fired, 24 times - meaning the ItemAdding EventHandler is
fired for each DocumentSet content type binded to the list, before finally giving the uploaded document the content type "Document".
The document library gets created by a ListInstance on deployment, and all the content types are being binded in this ListInstance.
Is this a bug? Or have I done something wrong?

Hi,
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thanks
Patrick Liang
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Patrick Liang
TechNet Community Support

Several Errors thrown when updating document class: 1046 3594 3590

1046: Type was not found or was not a compile-time constant: FullScreenEvent.
Warning: 3594: getStackTrace is not a recognized method of the dynamic class Error.
Warning: 3590: void used where a Boolean value was expected. The expression will be type coerced to Boolean.
Does anyone have any experience with these errors being thrown?
package {
     import flash.display.*;
     import FluidLayout.*;
     import flash.display.Sprite;
     import flash.display.StageAlign;
     import flash.display.StageScaleMode;
     import flash.events.Event;
     import gs.*;
     import gs.easing.*;
     import fl.motion.easing.*;
     import com.greensock.*;
     import flash.events.MouseEvent;
     public class Website extends MovieClip {
          public function Website() {
               /* Set the Scale Mode of the Stage */
               stage.scaleMode=StageScaleMode.NO_SCALE;
               stage.align=StageAlign.TOP_LEFT;
               /* Add the symbols to stage
                           var bg = new Background();
                           addChild(bg);
               var top = new top();
               addChild(top);
               var toprightoption = new toprightoption();
               addChild(toprightoption);
               //var middle = new Middle();
               //addChild(middle);
               var btmrightfooter = new btmrightfooter();
               addChild(btmrightfooter);
               /* Apply the alignment to the background
                             var bgParam = {
                                 x:0,
                                 y:0,
                                offsetX: 0,
                                  offsetY: 0
                             new FluidObject(bg,bgParam);
               /* Apply the alignment to the top */
               var topParam = {
                                  x:0,
                                 y:0,
                                  offsetX:0,
                                offsetY:0
               new FluidObject(top,topParam);
               /* Apply the alignment to the toprightoption */
               var toprightoptionParam = {
                               x:1,
                               y:0,
                                 offsetX: -toprightoption.width - 20,
                                offsetY: 20
               new FluidObject(toprightoption,toprightoptionParam);
               /* Apply the alignment to the content
                            var middleParam = {
                                x:0.5,
                               y:0.5,
                                offsetX: -middle.width/2,
                                offsetY: -middle.height/2
                            new FluidObject(middle,middleParam);
               /* Apply the alignment to the btmrightfooter */
               var btmrightfooterParam = {
                                x:1,
                                y:1,
                                offsetX: -btmrightfooter.width - 10,
                                offsetY: -btmrightfooter.height -10
               new FluidObject(btmrightfooter,btmrightfooterParam);
     private var currentlyShowing:MovieClip=null;
          public function showModalContent(clip:MovieClip):void {
               if (currentlyShowing!=null) {
                    removeChild(currentlyShowing);
               currentlyShowing=clip;
               addChild(currentlyShowing);
          public function removeModalContent():void {
               if (currentlyShowing!=null) {
                    removeChild(currentlyShowing);
                    currentlyShowing=null;

1. import the fullscreenevent.
2. click file/publish settings/flash and tick "permit debugging" to see which lines are generating the other two errors.

Approval template not working on update

Dear All,
I created an approval procedure to check line discounts >=25% on marketing documents. I used the below query;
'SELECT DISTINCT 'TRUE' WHERE $[$38.15.NUMBER]>=25'
On Adding new marketing documents the approval works well, BUT if i recall the same document and change the discount value then Update, the approval procedure does not work. When i open the query it returns TRUE based on that marketing document form.
Could this be a bug or is there something that i am not doing correctly?
I am on SAP Business One 9.1 PL05.
Regards,
G.W

Hi,
Approval procedure will not work for updated documents even if the query get correct result.
This is standard system design for approval procedure.
Thanks.

RE:Approval Templates Terms Based on queries (Requires Urgently plzzz ..)

Hi You All,
As per requirement we developed the small Addon which is attached to sales quotation & for that AddOn I need a approval which is on based userdefind query.I done this much of portation BUT as per standard. in Approval Template-Setup we have to select Document from Document Tab.but I dont have these std Document I need appproval on that developed AddOn
Rgs,
-Dinesh

Hi Dinesh,
U cannot find ur user forms in the standard approval list.
Regards,
Vasu Natari.

Approval template for line item price variation

Any recommendation on how to managed price variations at a line item level with using approval templates? The approval templates currently only allow for TOTAL document differences.
A senario as follows
1. Purchase order with line item price created
2. GRNI created (and unit price changed)
3. AP invoice created - AP approval template kicks in advising that there is a price discrepancy at a line item level between the Base and target documents.

Hi!
You can achive this via Stored Procedure.
Approval Procedure will not work for Row Level.

I am enrolled in an online university program that uses Sakai. Fire Fox updated something that attaches computer script to my Word documents when I upload them.

I am enrolled in an online university program that uses Sakai. Fire Fox updated something that attaches computer script to my Word documents when I upload them. I use a PC and Word 2010

sigh...this is quite idiotic, but I have found a solution. It was quite simple, really, and yet quite idiotic. I share it for all those reading so that, if you know of anyone else that did what i did, you can easily be the "hero" in their lives.
After a continued search via youtube or what have you for any possible solutions, I kept coming back to the fact that I was told by my computer that I didn't have "permission" to do the file deletion. I stumbled upon a youtube video that talked about "unlocking", "locking", certain files and what not.
Long story short, the reason why I couldn't do anything to the files that were on my desktop was due to my "locking" the desktop folder. I must have done this a while back not knowing what I was doing nor the ramifications of clicking a simple box.
I undid this by:
Opening Up Finder
then, going to MacHD --> Users --> My Account Folder
clicking on Desktop Folder, I "cmd+I"
I then, unclicked the "locked" option
I went down to the cog/settings and selected "Apply to enclosed items"
resulting then in having all my files on my desktop free accessiblity and delete-ability....
oi...at least I now know what "locking" a folder (even the desktop folder) can do to other files held within it

Page based on template don't update image path

When I create a new page beased on a template in the
templates folder some of the image paths don't update.
A div in the template has the following style code
"background-image: url(../images/leftframe.png);
background-repeat:repeat-y".
When the new page is created, and before it is saved in the
correct folder the code turns to: "background-image:
url(file:///MYDISK/CLIENTFOLDER/client_webpages/images/leftframe.png);
background-repeat:repeat-y".
This is perfect, because the new page still don't know its
correct path. But in CS3, and earlier versions of Deamweaver the
path was updated when the new page was saved. That does not happen
in CS4.
Linked css files and other image and file paths are updated
as it should, but this div style is not.
I know the work arounds; move the div style code to the css
file, open the html page in an other html editor correct it and
paste it back...
I don't want to spend time changing my templates or perform
work arounds when it is obvious that there is a bug in CS4.
Others with the same experience or a way to solve the
problem? Or should I send Adobe a bug report?
Stavanger

> I know the work arounds; move the div style code to the
css file, open the
> html page in an other html editor correct it and paste
it back...
Here's a better one - make the link root relative rather than
document
relative.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"Mr. Stavanger" <[email protected]> wrote in
message
news:gmu4dv$i4q$[email protected]..
> When I create a new page beased on a template in the
templates folder some
> of
> the image paths don't update.
> A div in the template has the following style code
"background-image:
> url(../images/leftframe.png);
background-repeat:repeat-y".
>
> When the new page is created, and before it is saved in
the correct folder
> the
> code turns to: "background-image:
>
url(file:///MYDISK/CLIENTFOLDER/client_webpages/images/leftframe.png);
> background-repeat:repeat-y".
>
> This is perfect, because the new page still don't know
its correct path.
> But
> in CS3, and earlier versions of Deamweaver the path was
updated when the
> new
> page was saved. That does not happen in CS4.
>
> Linked css files and other image and file paths are
updated as it should,
> but
> this div style is not.
>
> I know the work arounds; move the div style code to the
css file, open the
> html page in an other html editor correct it and paste
it back...
>
> I don't want to spend time changing my templates or
perform work arounds
> when
> it is obvious that there is a bug in CS4.
>
> Others with the same experience or a way to solve the
problem? Or should I
> send Adobe a bug report?
>
> Stavanger
>

Approval Procedure Not Triggered on Updating Document

Hi,
When Adding a new Sales Order, if the document meets the criteria laid down by an Approval Template, the Approval Process is started.
However, if an old Sales Order is Updated, the Sales Order the Approval Process is ignored.
This is a problem for certain customers who have Approval Procedures which prevent users Adding Sales Orders which would take a Business Partner over the Commitment and/or Credit Limit.
The user can get around the Approval Procedure by adding a Sales Order for a value which keeps the BP under the set limit. If they then Update the Order, they can enter any value.
For example, a user may be prevented from adding an Order totalling £1000.00. If they Add the Order for £0.00 instead, they could later amend the Order to any amount as the Approval Process is not fired !

Could you clarify what you mean by "The credit limit exceeded is in negative numbers"
Negative number: the system message I get when I create a delivery note for a customer, exceeding the credit limit is the following:
Customer has exceeded credit limit - 95.479 EUR
Customer has exceeded commitment limit - 95.479 EUR
Continue (Y/N)
Make sure the Credit Limits are set in the BP Master. --> OK, credit limit is set to 100 EUR, Commitment limit to 100 EUR
Also use Great than in Ratio and try to use a small number like 10 in the value --> I am using 1 EUR
Also, check in System Initialization > General Settings..BP Tab Activate approval procedure is checked. --> it is checked.
Using the range option does not solve the problem, in fact even if I use 'Deviation from Credit Limit does not equal 1 EUR' the approval is not triggered. When I use the same Approval template, but I alter the terms to Total document greater than 1 or Discount% greater than 1 the approval is triggered.
Edited by: Rui Pereira on Apr 29, 2009 1:19 PM

Print Templates print preview window closes unexpectly when printing document

This is a cross posting from Internet Explorer Web Development after a suggestion that this forum would be a better location. See
https://social.msdn.microsoft.com/Forums/ie/en-US/351e1245-b606-4467-9f3c-1c72f9cdf9ea/print-templates-print-preview-window-closes-unexpectly-when-printing-document?forum=iewebdevelopment.
I have raised an issue through Connect for this:
https://connect.microsoft.com/IE/feedback/details/1134168/ie9-to-ie11-print-templates-print-preview-window-closes-unexpectly-when-printing-document, but I would like some more visibility of the issue as my customers thought my application was closing when
they printed a document. I also don't know if an issue in Connect gets any priority support via MSDN, but this forum does.
This looks to me like a problem in the IE Print Templates startDoc API call, but if there is a more appropriate forum to raise this issue in please let me know.
In the application where I use print templates, the window closing is not in it self a problem because the Javascript that is calling startDoc also closes the Print Preview window when the print is finished.
The fact that the application looses focus and can be hidden by the windows of other applications when the Print Preview window is closed by startDoc is the issue noticed by our customers, so I need a fix preferably, or a work around at a pinch.
Details of the issue reproduced below.
When using IE Print Templates, the startDoc function is causing the print preview window to close. This behaviour started with IE9, and is still present with IE11.
When an application is using print templates (see
https://msdn.microsoft.com/en-us/library/aa753279(v=vs.85).aspx) for print functionality, this has the effect of causing the application to become hidden by any other application window once printing from the print preview window has started. It is
actually this behaviour that started me looking at this issue as the users thought the hosting application had closed.
Print Templates are not accessible by using IE as a web browser, but only when using the WebBrowser Control to embed IE in an application. The reference for this feature is available from this url:https://msdn.microsoft.com/en-us/library/aa753279(v=vs.85).aspx
and a sample Microsoft application that demonstrates the use of Print Templates can be used to demonstrate the problem (required for the reproduction steps). The application is available via this article and searching for "download spiffy".
Steps to reproduce the problem:
To see the full effect of the issue, first ensure there is a window from another application (like Windows Explorer) that will cover the sample applications window if brought to the foreground (making the Windows Explorer window full screen works).
Start the sample application (and ensure that the full screen Window Explorer is the next application to activate).
Then in the drop down box in the top right corner of the UI select Template8.htm.
Click the Print Preview button that is just below the drop down box (this will open a new Print Preview window).
In the new window click the Print… button (this will open a Print dialog).
Click the Print button at the bottom of the Print dialog.
The Print dialog closes (expected) and then the Print Preview window also closes (not expected), however the document is still printed successfully.
When the Print Preview windows is closed unexpectedly, the Windows Explorer window is brought to the foreground (obscuring the sample applications window).
If you reselect the sample application and click the Print Preview button again, the Print Preview dialog is not displayed unless you restart the application (this looks to be a symptom of the same issue, not a separate problem).
To see that the Print Preview window appears to be closed by the startDoc call, use the resource editor in Visual Studio (the exe can be opened directly by File | Open | File…) to edit the HTML resource "TEMPLATE8.HTM" (I found I needed to delete
it and add it back in for the change to stick), find the startDoc call and add two alerts, one on the line before and one on the line after. When IE is accessing the template, it is being done using the name of the executable (so do not rename the modified
version of printtemplates.exe, make the changes to a copy in a different directory if you don't want to change the original). Start the modified version of the application and follow the same steps as in the reproduction. This time, after clicking
the Print button in the Print dialog, the dialog will close, the first alert will pop up, then the Print Preview window will close, then
the second alert will pop up.
Thank you,
Warren.

Hi Shu,
I have noticed that the print templates API is listed as part of the Legacy APIs.
Is this just because it hasn't changed or is not new? Or does this mean that it is no longer maintained and may be removed (or at least deprecated) at some point in the future?
It would good to know if we should start planning for the implementation of a different method of printing.
I understand that the sample application is no longer maintained, but I also think that the Print Template API that it uses has not changed, and so should still work (and it does mostly).
If the Print Preview window was being closed as a result of using the Print dialog (and if it had behaved the same way with IE8) I would be willing to go with the by design argument.
I have found that the Print Preview window is not closed until startDoc is called, and it closes before control is returned from the startDoc function.
Just as part of investigating and try to find a workaround, if I call window.close(), any alert calls made no longer display the alert window after the close call.
Alert still functions after startDoc has closed the window however.
The is not the sort of consistent behaviour I would expect from something that is by design.
Also while investigating, I found that calling startDoc after calling window.close() results in an exception with the error code -2147467259 (0x80004005), this is probably quite normal and expected, but does indicate that the Web Browser Control should
not be closed till after printing.
I had found that old thread, and I had concluded it was the same issue, but it was also aimed at different aspect of the problem (which I see in the sample application, but not my application).
The visible issue I have is that my users think the application has been closed because after clicking print (on the Print dialog) the application gets hidden by other windows from other applications.
This aspect affects the sample in the same manner and so it was a convenient way to demonstrate the problem.
If IE connect do not look at this issue any time soon, do I have any other avenues to resolve this issue?
Thank you,
Warren.

OOTB approval worfklow not creating task when require checkout is set as Yes on the document library

HI,
I set the document library versioning to "require check-out" to yes.
I set the workflow settings to create an approval workflow and "start the workflow when the item is created".
I create a new document from the document template, save and check-in. The workflow task is not getting created, however the workflow is started.
when i change the require check-out to "No" and create a new document as above, the workflow tasks are getting created.
Can someone advise on what is the problem when versioning is enabled?? can anyone provide solution. thanks.

Hi,
According to your description, my understanding is that the task was not created after the approval workflow was running when setting the require check out to be yes.
I tested the scenario in my environment, if I used the Office client application to create documents, then the task would not be created even when the workflow was running.
There may be some reason that the creating task action is missed when the document is created using Office client application and the require check out is set to be yes.
As a workaround, I recommend to install Office Web Apps and use Office Web Apps to create the documents when setting the require check out to be yes.
The workflow will be starting before the documents is checked in, and it will create the task after the document is checked in.
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

Links when using Templates don't work in preview

I have created a template for the 'traditional' top banner,
left navaigation buttons site. In preview mode, any links
(navigation area or not) that point to another page in the web site
do not work, but external links go. (No error is reported, but
nothing happends) However, when published, all links work. Any
ideas what is happening?
Eample link:
<a href="../catalog.htm" target="_self"><img
src="../_derived/catalog.htm_cmp_edge000_vbtn.gif" width="140"
height="34" border="0" alt="Catalog & Renewal"
/></a><br />
The graphic does appear for the link.
If it makes any difference, this is a convert FrontPage site
where I manually edited the html to import the pages into my first
Dreamweaver site.
Thanks in advance,
Carolyn Wood

> In preview mode, any links (navigation area or not) that
point to
> another page in the web site do not work,
This is how DW will work if you are using ROOT RELATIVE
links, *and*
temporary files to preview.
Here's an example -
* I create a page with a link to an image -> <img
src="/images/foo.gif">
(note that the image link is a root relative link - the path
says to go to
the
root of the site and look for the images folder because of
the leading
slash)
<img src="/images/foo.gif" (that's root relative - it
starts with the root
of the site)
<img src="../images/foo.gif" (that's document relative -
it starts with the
current location of the document)
* I preview that page with DW (since I am using temp files,
DW is kind
enough to realize that root relative links won't work in a
preview, and so
it converts them to document relative links when it builds
the temporary
file for the preview) -> <img
src="../images/foo.gif"> (I'm assuming that
your document is one level below the root of the site). In
the preview,
this page looks fine because the browser has no trouble with
the document
relative link - it knows where the file it just opened is,
and can follow
the path to the image).
* I then click on a link in the previewed page to another
page that also has
ROOT relative linked images --> <img
src="/images/bar.gif"> and suddenly
the image does not load.
Why? Because when you click away from the temp file DW just
built for you,
you have lost the benefit of the automatic conversion that DW
does with
root relative links, and the browser looks for this new image
starting from
the root of the hard drive, not the root of your site.
The solution is to not use root relative links, and to change
all your
existing ones to document relative.
To read more about this, go here -
http://www.macromedia.com/support/dreamweaver/ts/documents/site_root_rel.htm
http://www.macromedia.com/support/dreamweaver/ts/documents/document_vs_site.htm
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"cwood_wdpl" <[email protected]> wrote in
message
news:[email protected]...
>I have created a template for the 'traditional' top
banner, left
>navaigation
> buttons site. In preview mode, any links (navigation
area or not) that
> point to
> another page in the web site do not work, but external
links go. (No error
> is
> reported, but nothing happends) However, when published,
all links work.
> Any
> ideas what is happening?
>
> Eample link:
>
> <a href="../catalog.htm" target="_self"><img
> src="../_derived/catalog.htm_cmp_edge000_vbtn.gif"
width="140" height="34"
> border="0" alt="Catalog & Renewal"
/></a><br />
>
> The graphic does appear for the link.
>
> If it makes any difference, this is a convert FrontPage
site where I
> manually
> edited the html to import the pages into my first
Dreamweaver site.
>
> Thanks in advance,
>
> Carolyn Wood
>

Any way to turn off errors when updating pages from the template?

I'm using Dreamweaver MX. My site is huge. It's an intranet
spanning dozens of departments. Some of those departments have
subsites that don't fall under the intranet's control, although
they are embedded within our site's folder structure. When I make a
change to the template and update pages, every time I hit one of
those subsites I get tons of errors, from "template not found" to
"unmatched body tag". The errors that pop up each have to be
clicked on before the updating can continue. I get hundreds of
these.
Is there any way to make errors not pop up while updating
pages from the template? Or even to exclude certain folders from
being checked? (Cloaking doesn't do it.)

> I'm using Dreamweaver MX. My site is huge.
Both of these are problems, I'm afraid. Combining that with
templates is
really trouble.
> "unmatched body tag".
Errors such as this are definitely caused by errors in your
page itself.
Can you show me a page where you would get this?
> Is there any way to make errors not pop up while
updating pages from the
> template? Or even to exclude certain folders from being
checked? (Cloaking
> doesn't do it.)
Valid code will not produce these errors. Unfortunately, the
only way to
avoid them is to remove any validation hiccups from your
pages.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"abna" <[email protected]> wrote in message
news:f14ue2$pk5$[email protected]..
> I'm using Dreamweaver MX. My site is huge. It's an
intranet spanning
> dozens of
> departments. Some of those departments have subsites
that don't fall under
> the
> intranet's control, although they are embedded within
our site's folder
> structure. When I make a change to the template and
update pages, every
> time I
> hit one of those subsites I get tons of errors, from
"template not found"
> to
> "unmatched body tag". The errors that pop up each have
to be clicked on
> before
> the updating can continue. I get hundreds of these.
>
> Is there any way to make errors not pop up while
updating pages from the
> template? Or even to exclude certain folders from being
checked? (Cloaking
> doesn't do it.)
>

Approval templates don't fire when updating document

Similar Messages

Maybe you are looking for