Mass tests have shown that the InDesign^® Server option -purgetrigger does not result in any recognizable memory gain. Instead, frequent execution of the purge triggers led to early server crashes. We will therefore ignore the specifications of the -purgetrigger option from now on.

We also took this opportunity to switch off the -shutdowntrigger option. Server restarts should be done by the calling application (in most cases the PubServer) not by the InDesign^® Server itself.

Please note that both options are are still allowed and correct - but the settings are ignored.

We have succeeded in identifying and eliminating a whole series of memory leaks. With the usual tools for memory monitoring (Xcode Instruments, Visual Studio Memory Profiler, leaks, ...) we can no longer detect any memory consumption by the plugins.

German texts (German Reformed 2006) lead to a loss of memory during rendering. The loss is only 32 bytes - but since rendering is executed extremely often depending on the project settings a significant memory loss in the range of 1 GB / 10,000 products can occur here. This error has already been reported to and confirmed by Adobe. A solution is in the works - but will probably only affect InDesign 2024.

The priint:comet InDesign^® plug-ins and comet_pdf are now supporting the HTML and PDF Export Tags (H, H1-H6, P, ...) writing W2ML files.

Please note: In the current plug-in version, the export tags are not yet applied when opening a W2ML in InDesign^®.

My Web Image URLs have a long list of URL parameters after the file name:

abc.png?context=12345..xyz&...

I try to shorten this information with ////--kEllipsizeEnd. But unfortunately this does not work.

We mistakenly treated the URL '?' parameters as part of the file extension. But as the extension should not be removed or shortened, there was nothing left to shorten in the overall name. We now disregard the URL parameters when shortening the names. So abc.png?context=12345..xyz&... results in abc.png only now.

If I try to make the panel Page Templates narrower, InDesign reproducibly falls into an endless loop.

FXD

When I call table::insert_rows with a row index >= the number of current rows, InDesign^® crashes reproducibly. I know the index is 0 based etc. - but it doesn't have to crash, hm?

The row index is interpreted now as follows:

• < 0 : First body row
• ≤ All rows (incl. header and footer) : Last body row
• otherwise : 0-based row index (This also includes headers and footers)

The return value 1 (Product too large) in the Build Support Script for kChecksizeAfter causes InDesign^®: to crash

FXD

I have noticed with the latest comet revision, when I check-out a document (pubserver 4.2.0.3091.r20221221180534), and the Comet Notes panel is closed, all notes are set to hidden, regardless their visibility when I saved and checked-in the document to pubserver.

However, if I have the Comet Notes panel open when I check-out the document, all comet notes are set to visible, regardless of the visibility settings per note when I had checked-in the document.

This was a side effect of fixing a bug when importing notes from Neowise with W2ML documents and is fixed now.

Unfortunately, the Python function comet.link.collect sometimes returns incorrect results.

The bug is solved.

Using the python function CDocument.close crashes InDesign^®.

This bug is solved now.

If the list of 'Products of Document' contains new products (marked with +) only, InDesign crashes repeatedly during reorganization.

The problem was caused by the fix of Case 2569084 and has now been resolved now.

In the hyperlink::find1 function, a prefix can be specified in the crossRefName parameter. Only hyperlinks whose names begin with this specification are then found. Apparently, however, this does not work. If I leave the entry blank, the hyperlink is found.

This error has now been fixed.

Although my image placeholder has the correct image file, the placeholder is shown as 'Changed' in the 'To Dos' panel:

The error occurred because the variable gSyncChanged used in the sync script has no longer been evaluated correctly since version v4.2 of the plugins. The error has been fixed.

Using scope +4 or +8 will cause document::pdf_export to create all Comet Notes as PDF annotations in the generated PDF. This is great in itself - but unfortunately the resulting PDF is faulty and cannot be opened.

This problem is solved now.

Using scope +4 or +8 will cause document::pdf_export to create all Comet Notes as PDF annotations in the generated PDF. Unfortunately, notes are lost or placed on the wrong pages when exporting to single-page PDFs. This happens with all Comet Notes from right-hand document pages.

This bug is fixed now.

Using scope +4 or +8 will cause document::pdf_export to create all Comet Notes as PDF annotations in the generated PDF. But Comet Notes that are completely in the pasteboard are unfortunately not exported.

Comet Notes from the pasteboard are now also be created as PDF annotations by document::pdf_export. The icons are automatically placed directly to the left of the PDF pages.

Using scope +4 or +8 will cause document::pdf_export to create all Comet Notes as PDF annotations in the generated PDF. Apparently, the original opacity is also applied and icons of the annotations become quite pale. Can these icons also be displayed in 100% opacity?

We can. The annotion icons are now always created with 100% opacity.

The InDesign UI limits the width of table columns to 3pts. But with the cScript function table::resize_cols you could make the column width even smaller. Unfortunately, this no longer works since v4.3 R33833. We use these small columns (0.1pt) to keep table rows together in the same frame.

Yes, that's correct. We have adjusted this to the InDesign behavior as part of the fix for case #2763238 (Layout rule 'Table Break' changes column widths even in case of errors).

But the trick with the (almost) invisible columns to keep table rows together of course is cool. We don't want to get in the way and have now reduced the minimum width to 0.1 pt. But it really can't get any smaller and:

ATTENTION: Adobe can change InDesign^® at any time so that our little hack no longer works. We have no influence on this.

When connected to Publishing Server 4.4 / 2024/01, the Publication Information panel now shows basic document information if available:

• previews of spreads and pages are shown, if metadata has already been generated for the selected document
• the information text field shows a summary of notes applied to the selected document

Notes created in Neowise or priint:planner in W2ML documents were not imported (and therefore not visible), when the document was checked out and converted in InDesign. This is fixed.

The following improvements have been made to the Python integration:

New functions:

• CDocument.getID
• CDocument.setID

For rectangles (type 0), the frame::get_type function unfortunately returns the value 4 (kSpline).

This statement is not quite correct. The function correctly returns the value 0 (kRectangle) for rectangles. The result is only incorrect if the rectangle is a square.

We have therefore defined the new frame type kSquare now. And there is now also the new type kCircle for circles.

It's only a very small thing: If I call frame::get_type with parameter totalPoints set to 0, InDesign® will crash.

This is fixed now.

If the product after a keepWithNext product not fits the current page, both products should be build-up on the next page. And of course both products should be removed from the first page. That works so far. Nice. But unfortunately only if the second product is already too large before loading - or, in other words, if the template of the second product is already too large for the current page. However, if the template fits on the current page and only becomes too large when loading, the product will not be deleted from the old page.

This is fixed now.

If the product after a keepWithNext product not fits the current page, both products should be build-up on the next page. This is done correctly. But unfortunately the new pair is placed at a wrong y-position in the new 1:N element if the height of the second product was changed in a 'After Build' layout rule in the first try.

This is fixed now.

If I call document::open with a document that is already open but not shown, no document window is shown at all, even if I set the visibilty parameter to 1. This case occurs, for example, when I update the Crossref Placeholders of all documents in an InDesign^® book. To do this, all documents in the book are opened in a loop and the placeholders are updated in each case. However, to find the targets of the cross references, all documents in the book must also be opened (in the background). So if your loop is supposed to open the second document of the book, this document is already (invisibly) open. But since it is not made visible, no placeholders are updated from the second document onwards.

This problem is fixed now.

Assume the same situation as described one line above and to work around the document::open bug you are calling an extra document::show. Unfortunately, the Crossrefs are still only updated in the first document of the book loop.

Yes, this is because the background opening of the documents of the book by hyperlink::find1 marks the documents as 'Do not save when closing'. From the perspective of hyperlink::find1 this is correct because the documents are only opened in order to search in them. hyperlink::find1 cannot 'know' that the documents are still to be changed later.

To solve the problem, you now can set parameter findInBook of hyperlink::find1 to 2. In this case the automatically opened document are now marked as 'save before close'.

With frame::set_corner I can set all corner types supported by InDesign. But unfortunately the rectangle corner (plain) and the radius 0.0 do not work.

This is fixed.

The documentation says that I can set a small selection of text formatting without using TaggedText: This is actually quite pretty and essentially works. Only the text color with the help of a defined swatch color does not seem to work.

This is fixed now. Don't forget to enclose the swatch names by single quotas in this case :-)

frame::replace (fr, "abc<cColor:'blau', 50.0>def<cColor:>ghi");

I update all cross-reference placeholders of all documents of a book in a loop. If I do not close the documents in this loop after opening and updating them, InDesign crashes at the end of the loop.

To update the cross-references all documents of the book are opened automatically in the background. It is assumed that theses documents are only used for reading and are not changed - in this case we can close the documents immediately (and don't have to wait for the next idle time, as InDesign normally does). Changed documents cannot be closed in this way - this leads to a crash. Unfortunately, there is nothing we can do about this problem.

However, we have extended the hyperlink::find and hyperlink::find1 functions so that documents opened there can be saved automatically when they are closed. To do this, enter the value 2 (instead of 1) in the findInBook parameter.

Unfortunately, the function document::select_by_name does not work if the document path contains German umlauts (äöüß). The error only occurs on the Mac.

The problem was that in this case the 'umlauts' were given by InDesign as so-called combining characters. For example, instead of ü (UTF8 : C3 BC) we got u ̈ (u + COMBINING DIAERESIS (UTF8 : 75 CC 88). The fact that this spelling still exists is quite astonishing.

The problem is solved now.

The run_python function can be given variables of the current script. This is super helpful. Thank you! Unfortunately, the transfer does not work for variables of type IDTypeList.

This is fixed.

Unfortunately, the file::download_webimages function does not work for URLs that contain a user name with password.

This is fixed.

Please note: For technical reasons, images loaded with file::download_webimages must be loaded with the kNoHash option. Otherwise the images will be loaded again when used as Web Images.

In the following situation, InDesign crashes reproducibly:

1. Select a Page Element in panel Page Elements
2. Change the elements name
3. Without leaving the name field select a new element in the elements list (but not by selecting the element directly in the document).

This is fixed.

I have just noticed that in the Python documentation all method entries are displayed twice in the sidebar.

The documentary now looks right again.

When placing PDF-files that have a white background using the Python-method CFrame.setImage, it seems like the white background can’t be changed to be transparent. In the rendered PDF-file the placed PDF has a background.

For CScript there is a parameter in the method frame::place_pdf_with_crop with the parameter transparentBkg the background can be changed to be transparent instead of white.

Is there a way to do this native in Python?

That was easy to solve - the option already exists, but is not yet documented. With the function CFrame.setImage there is already a keyword kTransparentBackground to set this, here is an example:

comet.gFrame.setImage (
 	'$DESKTOP/Unbenannt-1.pdf',
 	options = { 'kTransparentBackground' : True })

Documents with a right-to-left binding (e.g. Arabic or Hebrew) are not shown correctly in the Planner. In the spread previews, the right document page is shown on the left and the right-hand side of the previews remains empty.

The reason for the incorrect previews is that the snapshots that we are taking from the spreads always start at the first page of each spread. But if the pages are arranged from right to left, the top left corner of the spread must be the top left corner of the last page of the spread.

We have fixed that problem. But please note: In 'normal' InDesigns®, the UI elements for setting the page binding are hidden and a so-called ME version is required to set or change the page binding. On the other hand, every 'normal' InDesign® version is able process the settings of a ME version.

We have tested the basic functions of the priint:comet plugins in a right-to-left document (product build-ups, updating placeholders, drag and drop, Products of Document, ...). It all seems to work. However, we cannot guarantee that everything in these documents will work correctly and as expected. We expressly reserve the right to regard these not as bugs but as (possible chargeable) feature requests. We hope you understand that.

As described above, the page binding can only be set or changed from left to right to right to left in special ME versions of InDesign®. Here is how you can still change the page binding in normal InDesign^® versions too:

• Parameter pageBinding of function document::create
• Javascript : app.documents[0].documentPreferences.pageBinding = PageBindingOptions.RIGHT_TO_LEFT;

In addition to that, we have added the new menus:

• Font -> Page Binding -> Left - Right
• Font -> Page Binding -> Right - Left

The following improvements have been made to the Python integration:

• The following functions now additionally accept tuple[int, int, int, str] for the recordID parameter(s):
  • placeholder.link
  • placeholder.load
  • placeholder.store
  • CFrame.link
  • CFrame.load
  • CFrame.store
• placeholder.link parameter length now has a default of -1 to prevent confusion when loading text placeholders
• placeholder.load parameter start now has a default of -1 (Load all placeholders)
• runCScript has a new parameter logExecution (default False) to disable logging about the script run (execution time, script ID etc...)

• run_python parameter flags can now be used to disable logging about the script run (execution time, script ID etc...)

I'm using frame::gettext and frame::replace to transfer the content of a text frame to another frame. Unfortunately, this destroys some of my placeholders.

frame::gettext (gFrame, str, 0, -1, 3);
frame::replace (fr, str, 0, -1, 0);

The problem is caused by a 12 (!) years old fix when importing incorrect %!TT text. We have improved this correction so that it can also solve these new situations.

Our designers are Mac users, and we are wondering if it's possible to update the tool-tips to include Mac keys. For example where it says "ALT", can it read "ALT/OPTION"?

We have changed this to "OPTION" on the Mac.

With document::select_by_name I can bring documents to front. I can specify the path or the name of the document. Is this also possible via the window title (Display Name)?

We have extended the function so that a single name without a path separator can also be the window title.

I change the front document using document::select_by_name in my script. But gDocument continues to point to the old front document.

Yes, that corresponds to the documentation of gDocument. In older plugin versions, gFrontDocument was automatically adapted to a changed front document. Unfortunately, this form of pseudo-function is no longer possible in the cross-environment of cScript and Python.

To work around this problem, we have extended item::define so that you can also change gDocument according to the new front document. You will find an example in item::define.

Checking or updating 30 Web Images of a document takes an extremely long time (90 seconds) the first time after restarting InDesign^®. Repeating the action only takes 1.5 seconds - even if I delete all downloads first. If I then re-tart InDesign^® again, it takes 90 seconds again the first time.

The problem occurs only on Windows and it took us a long time to find the reason. Apparently CURL needs a very long time for the first handshake to the host in InDesign on Windows. And the behavior only occurs in InDesign^® (and Illustrator^®) but not in comet_pdf.

The problem seems to have been known for some time. Here is a link to an (unresolved) discussion from 2013 (!):

HTTPS CURL get slow when calling at first time

We conclude that this is a handshake problem with http connections. Once a host connection has been established, it is cached and can then be used again faster. Whatever the reason for the long handshakes in InDesign is - we've implemented a workaround for this behavior. 

Using InDesign^® with Plugins 4.3 R ≥ 33632 I get a crash when updating Web Images which have already been downloaded once.

FXD

And another very ugly problem with the Web Images: Downloading more than 100 Web Images at the same time failed on Windows.

Aargh - the problem was caused by the OpenSSL version used and could be fixed (with great effort).

The function file::download_webimages seems to ignore the settings of the Web Image proxy. The proxy I have defined using prefs::webimage_set_proxy resp. manually by using prefs::webimage_proxy_dialog.

If the proxy is activated, it is applied now in file::download_webimages too.

After downloading a lot of Web Images using file::download_webimages, I can set the parameter updateFlags of frame::image to 16 to suppress an additional file checking. Is this parameter also available for frame::link_url?

frame::link_url now also have a parameter updateFlags.

I have a Python script which is supposed to re-link all placeholders of a document to a different string id:

 comet.placeholder.link(
	frame, 
	id, 
	autoLoad = True, 
	applyLayoutRules = True)

The ids of the placeholders are changed as expected, but when I pass the paramter autoLoad=True only some of the frames are updated with the new contents, and, for text frames, only some of the placeholders in the frame are updated.

• Text placeholders are only updated when they are at the beginning of the text frame (startPos = 0)
• Text placeholders are NOT updated if there is some untagged text beforehand.
• Only the first text placeholder of a frame is updated (if at all, see above)
• Image frames are not updated at all.

The reason your text placeholders were not loaded was because the default of the parameter length was 0. Using -1 for the length parameter should properly load all text placeholders aswell. Image placeholders not loading was indeed a bug.

I improved comet.placeholder.link in the following ways:

• Parameter length now has a default value of -1
• Image placeholders should now be properly loaded when parameter autoLoad is True
• The parameter ID now also accepts type tuple[int, int, int, str] for convenience

Clipboard variables stored in cScript with the type KeyValues generate an error when retrieved in Python.

Store a key-values list in cScript

KeyValues 	kvs = keyvalues::alloc();
int 		errid = 0;

keyvalues::put (kvs, itoa(error_id), serror(errid));
set_script_clipboard ("my_kvs", kvs, "KeyValues");

Fetching the stored list in Python leads to an error

your_kvs = comet.getScriptClipboard ("my_kvs")

This is fixed.

When executing the CPage.getPageItems function, I noticed that the function seems to cause an error:

ERROR
 An exception occured:

Type: <class 'SystemError'>
Information: <method 'getPageItems' of 'CPage' objects> 
   returned NULL without setting an error
				

FXD

When executing file::download_webimages, incorrect log outputs are generated:

• In a test with 29 (different) URLs, there were 29 different paths in the resulting IDTypeList. I was also able to find 29 different files there.
• However, not all 29 different URLs are listed in the logs; some are repeated and others are not mentioned at all. Are the files mentioned several times actually downloaded or is this perhaps more a behavior when writing the log lines?
• I also noticed lines in the logs with a special character and a truncated URL at the beginning of the line. Do these lines mean something specific? In one file, the end of the file name was chopped off. If I remove / correct the corresponding lines, I get the correct number of files again. So it only seems to affect the logs.

These problems arise because 'many' processes (here 29) are writing into one log file more or less at the same time. We removed the logs for this function.

Web Images with nameflag kOnlyHash getting incorrect file names

This is fixed.

When I run a reorganization, products that need a template change lose their magnets if the Layout Rules of the new template also do some 'Move to Layer's.

This is fixed.

In the Special Cases of the panel 'Products of Document', there is the 'Move to Layer' action. Unfortunately, nothing is executed when you click on the 'flag' button.

The button works again now.

Using the Python integration, the global vars comet.gStart and comet.gLen are not set when in the sync context of a placeholder (i.e. comet.kContextPlaceHolderSync). Both values are always set to their defaults of -1.

This is fixed now.

The Python function comet.link.collect seems to find the same links multiple times, depending on how many pages are in the document.

Fixed

Some of the rule tags defined for TT texts are not working. For example, when specifying %MTT... the text is inserted unchanged.

The problem occurs when reading from the tags (placeholders) is switched off by the user. It's solved now.

For some time now, the dimensions of tables in the TaggedText to be imported can be checked (e.g. with %UTT). Unfortunately, this check classifies all tables as incorrect.

This is fixed now.

With marginRel set to 1, the function page::get_size does not work properly.

This is fixed now.

The documentation says that frame::color_rgb and frame::stroke_rgb both leave the color unchanged with the color definition -1, -1, -1. However, black is set instead. The same also applies to CMYK functions.

This problems are solved now.

If I use the function frame::get_overprint with what = kOverprintBasic, I always get 0 as the result for the overprint.

kOverprintBasic can be used in the frame::set_overprint function to set all three overprints (Stroke, Fill, Gap) in one call. Of course, it makes little sense to ask for three properties at the same time in the getter. We have now described this a little more clearly in the documentation and with the value kOverprintBasic, the function now returns the result -1.

The value for isolation of the function frame::get_blending seems to be wrong and always returning the knockout value.

This problem is solved now.

The functions for converting HTML to TaggedText (%!TT_html_, html::to_tagged) accept CSS color definitions in the forms

• <span style="color:#FF0000"> and
• <span style="color:gb(255,0,0)">.

Colors can now also be defined via the color name defined in the target document.

It would be helpful if the log file also contained the document path and the layer of a product build-up.

This is now being done.

When I use the frame::refpoint function, I get the same results for page-relative and spread-relative results.

The problem has been fixed now.

If I'm using document::saveas in comet_pdf, my w2ml is stored with the extension indd too. I know, can set the extension inside my script - but since InDrsign always uses indd and comet_pdf always uses w2ml - may be ist a good idea to do that in the document::saveas itself?

Okay, okay, we have done. You don't need to set an extension anymore. Take care: If you set an extension now, we will replace it!

Is there a way to specify the page number of the first page in document::create?

We have added the new parameter startPageNum to the function.

ATTENTION: We have taken this situation to revise the entire parameter list of the function. The parameters, their effects and descriptions should now be clearer.

The function productlist::get seems not to dive into sub-products, as it should be done for example in the following statement:

watched 
{   row2='Publication' 
  ? row2='chapter' or row2='Produkt' 
} 
row2='Publication' or row2='chapter' or row2='Produkt'

The error is contained in all releases greater than R33300 and has now been fixed.

In the panel Comet Admin -> Comet, there is a button at the bottom. It works pretty nice, really. But using Windows, the Windows Prompt window is displayed briefly each time. That's not bad - but is there any way to get rid of it?

Yes, we can. The 'problem' is solved now.

In the panel Comet Admin -> Comet, there is a button at the bottom left that can be used to create a PDF from the current document using comet_pdf. This button works nice - but not with comet_pdf based on PDFlib 10.0.0 on the Mac.

This 'problem' is solved now. As a workaround you can use any other version of comet_pdf on the Mac except the 10.0.0 based one.

In the //// part at the end of the Web Images download URL you have various options to configure the path and name for the local download file. See here for more information. For shorter but still unique names we added the new option kOnlyHash now.

Suppose I know which Web Images a product build-up will require. Would it be possible to load these images before the build?

The new file::download_webimages function is now available for this purpose. The function loads the images in parallel and is therefore up to 50 times faster than sequential downloads.

The new page::set_size function can be used to change page sizes in both InDesign® and comet_pdf.

Bitte lesen Sie vor Verwendung unbedingt die Hinweise zur Funktion!

frame::image automatically creates a Web Imags if the given image path is an URL. If the local download file for the URL does not yet exist, it is downloaded automatically. If the file already exists, the system checks whether it is still up-to-date before inserting it into the document.

Can this check be switched off? This would be useful, for example, for multiple used logos.

The function frame::image has been given the new parameter updateFlags for this purpose. The value 16 prevents the check.

I'm creating a color using the Python function comet.color.createCMYK. If I then use comet.kColorModels[color.getModel()] to get the color space of the new created color, I get the answer kColorModelLAB.

This is fixed.

I'm using comet.color.createLAB to create a Lab color. But I'm always get an excection.

This is fixed.

I'm using frame::create with type kLine to create a line in the document. But I always get a frame.

Yes that's right. As the docu says, if you give us a column number > 0 we will create a rectangular frame. But anyway, we have now changed the behavior: If you give us a kLine, we now ignore the column number - and create a line.

The layout rule 'Fit Frame' does not work on master pages. The same applies to the frame::fit_better function.

It's because the frames on masterpages does not have a page. But we need the page in some edge cases, when the frame falls to another page of the spread due to the fitframe-action.

Okay, but it is no problem to ignore these edge cases in master pages. In the this release, fit frame will also work on masterpages.

I am trying to load sub-products of the Product Pool with an SQL statement of the following type:

(select ...)
union
(select ...)

In doing so, I get the error "Error while executing script".

The error occurs due to the (relatively) new option of loading sub-products by scripts. To do this, we need to check whether a statement is SQL or a script. We had overlooked the fact that SQL can also begin with '('. The problem has been fixed.

The help texts for the products of panel Product Pool contain so-called 'Placement Information'. What is the purpose of this information?

This information is still from the (old) grid based product build-up and no longer has any meaning. The information has been removed.

Even if I cancel the 'Replace Elements by Grid...' dialog of panel 'Page Templates', all existing frames of the document are removed. The page template is then empty.

The problem is solved now.

Workaround : Do a simple "Undo" :-)

When I want to delete a page template, I get two almost identical warnings. And although I held down the Alt key, nothing is deleted afterwards.

Yes, the Alt key must still be pressed when confirming the first warning. This is in fact not necessary. The first warning has therefore been removed and the Alt key is requested before the dialog appears.

The function Python CFrame.hasOverset always returns False even if the given frame has no overset at all.

FXD

Missing closing <in:> resp. <w2inline:> tags in TaggedText lead to an infinite loop of InDesign.

Before importing TaggedText (e.g. %!TT), 'newer' plugins automatically replace all <in:> tags by (text-position safe) <w2inline:>'s automatically. At this transformation, we are looking for the closing <in:> - and all text between the two tags are taken as the (text) content of the w2inline. Okay, you can see where the rabbit is going ... :-)

The fixed plugins will check this situation and generate the following output in case of missing <in:>'s:

ATTENTION - END OF LIFE plug-ins for InDesign^® 2020 and 2021

This is the last REGULAR release of the priint:comet ID plug-ins for InDesign 2020 and InDesign 2021. Bug support for InDesign 2020 and InDesign 2021 will be discontinued at the end of April 2024.

As announced in the previous release, search fields are now supported for custom publication search methods, the 'prototype' checkbox has therefore been removed.
Labels, input types and default values are defined in findstatements and thus can be used with any data connection.
A detailed description, how to implement find statements for the Product and Publication panel, define and evaulate search fields in the PublishingServer environment can be found here.

The Placeholder Variants are a nice, but unfortunately completely unknown tool. However, we have slightly improved the dialog for creating a variant: Instead of the name option @*, there is the checkbox 'Global for Everone' now.

When creating a Placeholder Variant, you can enter a description for the variant. Where is this text used?

The description is now shown as help text for the variant in the Placeholder panel.

Publications can now also be searched server-side. To do this, activate the checkbox to the right of the search method. You can then specify up to four //-separated search parameters in the edit field of the search.

The search parameters are evaluated on the server side. So to get the correct search results, the search must also be extended on the server side.

This is a pilot project of server-side publication search. If this search proves successful, the search fields will be implemented as configurable and separate input fields.

See History of v4.2

See History of v4.2

New cScript function "server::load_elements executes the standard build script of a multiframe placeholder in a PublishingServer environment.

This is the first official release of priint:comet ID plug-ins v.4.3.