- This topic has 5 replies, 2 voices, and was last updated 12 years, 10 months ago by
.
-
Posts
-
Hi
I just upgraded to 1.4.2 and I can’t seem to select the file extension property anymore under the Properties tab. How am I suppose to use php code then?
/Linus
I’m not aware of any code changes in 1.4.2 that affect the File Extension property. Can you provide me some details to help evaluate:
0) are you able to access the File Extension property in Properties window?
– if no, click the top node in the outline view to see the File Extension property
– what specifically happens when you select a new File Extension property and then generate code from either Project>Generate HTML menu or use the Run in Test Center actions?1) can you post an example design file that is affected
2) any screenshot or step-by-step directions to replicate are appreciated
@support-wayne wrote:
I’m not aware of any code changes in 1.4.2 that affect the File Extension property. Can you provide me some details to help evaluate:
0) are you able to access the File Extension property in Properties window?
– if no, click the top node in the outline view to see the File Extension property
– what specifically happens when you select a new File Extension property and then generate code from either Project>Generate HTML menu or use the Run in Test Center actions?1) can you post an example design file that is affected
2) any screenshot or step-by-step directions to replicate are appreciated
0) The only property window I found is the one where I click the top node in the outline view and under -HTML header I try to use the scroll down menu for file extension. The scroll down menu doesn’t show anything, not even html.
1) I will attach the sample
2) You get a screenshot. What I did was to create some simple designs using the previous version, not much functionality, then upgraded when asked to and now it doesn’t work.
Thanks for sharing this with us. Our team is investigating and will update you as soon as we know more.
Apologies as we found the root of the problem in 1.4.2 based on the info you provide. Thanks very much for pinging us on this matter. The fix will be available by this time tomorrow. We plan to roll out a hot fix late today (ver 1.4.3).
