[oXygen-user] After Fluenta update the context menu action disappeared

[Franz-Josef Knelangen]

Hello,

the Fluenta context menu action in the DITA Maps Manager view disappeared after 
updating to Fluenta 3.3.

Reinstalling the plug-in didn't help, reinstalling Oxygen didn't help either.

Is there some temporary config file I have to change/delete to get this working 
again? Please, advice.

Greetings,
Franz-Josef

Franz-Josef Knelangen
Leiter Dokumentation


Direct:
Main:
Mobile:


+49 7634 5612-0
+49 7634 5612-0
-


Facebook | 
Xing | 
LinkedIn | 
YouTube


[cid:image002_01fef2d4-1f7d-4ea5-9727-748ef31e8852.png]


AKG Software Consulting GmbH
Uhlandstr. 12
D-79423 Heitersheim
www.akgsoftware.de


Gesch?ftsf?hrer: Dipl.-Ing. Artur K. G?nther, Dipl.-Ing. Arno Br?ggemann, 
Dipl.-Ing. (FH) Bernhard Feser, Dipl.-Ing. Jens G?nther
Sitz der Gesellschaft: Heitersheim, HRB 310383 (Amtsgericht Freiburg i. Br.)




___
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user

Re: [oXygen-user] Conkeyrefs not rendered on map-level

[Oxygen XML Editor Support (Radu Coravu)]

Hi Sasha,


Usually problems can be either editing problems or publishing problems 
or problems which affect both editing and publishing.



Currently I want to switch from Oxygen 23 to 25.0 including an 
extracted build-in DITA-OT3.x with custom pdf2 plugin but In the 
updated environment we have the following effect:



In almost all DITAVAL contexts (we have a lot) the variable texts are 
not rendered into the DITA Map anymore without error messages.


This looks like an editing problem, in such cases we are interested in 
knowing what those particular error messages state. Ideally we would 
also have a small sample DITA project to reproduce the problem on our 
side. You can do this with a separate off list email.


Just a few DITAVAL contexts produce output as before.


By output do you mean publishing?


In published content topics/chapters everything is fine -> conkeyrefs 
are resolved.


So the publishing is fine? Only the DITA Maps Manager has problems 
displaying the keyrefs?


Also Oxygen Author WYSIWYG resolves all conkeyrefs as expected in 
topics and in the map.



Ok, so the main editor area seems to work.



In the pre-processing output (…_MERGED.xml) the specific map elements 
do not contain the variable text but conref attributes with wrong 
transformed links:
The conrefs contain “path/topic.dita#ElementID” instead of 
“path/ditatopic.dita#topicID/ElementID”


In correct output contexts there are no conref attrubtes rendered into 
output, just the elements with resolved text.


So there is also a publishing problem as well? Oxygen 25.0 comes bundled 
with DITA OT 3.7 from what I remember, maybe there is some 
incompatibility between your custom PDF plugin and DITA OT 3.7.


Do you have also a DITA DTD specialization plugin? If so did you install 
it in the DITA OT bundled with Oxygen 25.0?


I guess, there could be many different reasons for this. I tried a lot 
and couldn’t reproduced the problem in a simple test project. I also 
did´nt manage to simplify our project to a working state.


I somehow suspect you may have some DITA specialization for certain 
topics. I'm not sure. If you can reproduce about the same problem when 
editing and when publishing, the problem is usually somewhere in the 
DITA Open Toolkit publishing engine, some plugin which may not be installed.



Regards,

Radu

Radu Coravu
Oxygen XML Editor

On 1/23/23 17:19, Sascha Nothofer wrote:


Hi DITA & Oxygen Users,

Currently I want to switch from Oxygen 23 to 25.0 including an 
extracted build-in DITA-OT3.x with custom pdf2 plugin but In the 
updated environment we have the following effect:



In almost all DITAVAL contexts (we have a lot) the variable texts are 
not rendered into the DITA Map anymore without error messages. Just a 
few DITAVAL contexts produce output as before.


In published content topics/chapters everything is fine -> conkeyrefs 
are resolved. Also Oxygen Author WYSIWYG resolves all conkeyrefs as 
expected in topics and in the map.


In the pre-processing output (…_MERGED.xml) the specific map elements 
do not contain the variable text but conref attributes with wrong 
transformed links:
The conrefs contain “path/topic.dita#ElementID” instead of 
“path/ditatopic.dita#topicID/ElementID”


In correct output contexts there are no conref attrubtes rendered into 
output, just the elements with resolved text.


I guess, there could be many different reasons for this. I tried a lot 
and couldn’t reproduced the problem in a simple test project. I also 
did´nt manage to simplify our project to a working state.



Maybe someone experienced a similar effect (conkeyrefs in topic 
content resolved but not in map title/data elements) and can provide 
hints for a possible cause and or solution.


What I can say so far:
- It has nothing todowith the custom pdfplugin: same problem with 
build-in pdf and html transformation scenarios.

- We are using only standard pdf parameter settings.
- It has nothing todo with filtering directly because I have deleted 
all filter atts in the conkeyref chain in scope of the problem. Also 
our props attribute specialization does not affect the problem.

- We do not use:

-  - scoped keys and ditavalref in maps

-  - push-replace

-  Same problem with and without DITA project files.

- Problem is not caused by DITA topic content structures (I have 
copied content from working to non-working context.


I'm curious if someone has already seen something like this.

Best Regards

Sascha





Kontakt | Contact   Rein Medical GmbH
T:  +49 2161 6984 - 131 Monforts Quartier 23
*M:*
Schwalmstraße 301
*F:*+49 2161 6984 - 231 41238 Mönchengladbach
*E:*sascha.notho...@reinmedical.com Germany
*W:*https://www.reinmedical.com 
*S:*



Rechtliches | Legal 
Geschäftsführer: 	Dieter Cyganek, Stephan Rein, Thorsten Godulla, 
Hisakazu Harada, Akira Suzuki

Registergericht:A