Skip to main content
T
TooLzor
Known Participant
October 24, 2018
Answered

Photoshop CC 2019 extensions missing while others are still there

  • October 24, 2018
  • 2 replies
  • 1759 views

I have 2 extensions, Layer Cake and Lazy Save.

In 2019, Layer Cake still shows up and works fine while Lazy Save does not.

I've more or less copied the manifest from Layer cake and renamed the extension stuff to Lazy Save and resigned and it still doesn't show up.

I'm at my wits end why this is happening.

<?xml version="1.0" encoding="UTF-8"?>
<ExtensionManifest Version="6.0" ExtensionBundleId="LazySave" ExtensionBundleVersion="1.0.0"
ExtensionBundleName="Lazy Save" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ExtensionList>
<Extension Id="com.CanuckleHead.LazySave" Version="1.0" />
</ExtensionList>
<ExecutionEnvironment>
<HostList>
            <!-- Uncomment Host tags according to the apps you want your panel to support -->
            <!-- Photoshop -->
            <Host Name="PHXS" Version="14" />
            <Host Name="PHSP" Version="14" />
            <!-- Illustrator -->
            <!-- <Host Name="ILST" Version="[18.0,18.9]" />-->
            <!-- InDesign -->
            <!-- <Host Name="IDSN" Version="[10.0,10.9]" /> -->          
            <!-- Premiere -->
            <!-- <Host Name="PPRO" Version="[8.0,8.9]" /> -->
            <!-- AfterEffects -->
            <!-- <Host Name="AEFT" Version="[13.0,13.9]" /> -->
            <!-- PRELUDE -->
            <!-- <Host Name="PRLD" Version="[3.0,3.9]" />   -->
            <!-- FLASH Pro -->
            <!-- <Host Name="FLPR" Version="[14.0,14.9]" /> -->
</HostList>
<LocaleList>
<Locale Code="All" />
</LocaleList>
<RequiredRuntimeList>
<RequiredRuntime Name="CSXS" Version="6.0" />
</RequiredRuntimeList>
</ExecutionEnvironment>
<DispatchInfoList>
<Extension Id="com.CanuckleHead.LazySave">
<DispatchInfo >
<Resources>
    <MainPath>./index.html</MainPath>
</Resources>
<Lifecycle>
<AutoVisible>true</AutoVisible>
</Lifecycle>
<UI>
<Type>Panel</Type>
<Menu>Lazy Save</Menu>
<Geometry>
<MinSize>
<Height>100</Height>
<Width>100</Width>
</MinSize>
                    <!--<MinSize>
                            <Height>550</Height>
                            <Width>400</Width>
                        </MinSize>
                        <MaxSize>
                            <Height>550</Height>
                            <Width>400</Width>
                        </MaxSize>-->
                        
</Geometry>
<Icons>
<Icon Type="Normal">./icons/LazySave.png</Icon>
<Icon Type="RollOver">./icons/LazySave.png</Icon>
<Icon Type="Disabled">./icons/LazySave.png</Icon>
<Icon Type="DarkNormal">./icons/LazySave.png</Icon>
<Icon Type="DarkRollOver">./icons/LazySave.png</Icon>
</Icons>
</UI>
</DispatchInfo>
</Extension>
</DispatchInfoList>
</ExtensionManifest>

tried editing the extensionManifest Version from 5 to 6 (saw in some other posts) both don't work for this extension...

I can't see any reasons for it, I'm not getting any errors or if I am they are totally silent and I can't find them...

This topic has been closed for replies.
Correct answer tomzag

Beside the MinSize you must also declare the "normal" size:

                    <Geometry>
                        <Size>
                            <Height>100</Height>
                            <Width>100</Width>
                        </Size>
                        <MinSize>
                            <Height>100</Height>
                            <Width>100</Width>
                        </MinSize>
                    </Geometry>

2 replies

T
TooLzorAuthor
Known Participant
October 24, 2018

Yeah I just sorted it out...I guess cause min and size were the same it just locks it at that size (which is...annoying but at least fixable)

Thanks for that...Never thought it would be a size manifest issue.

tomzag
tomzagCorrect answer
Inspiring
October 24, 2018

Beside the MinSize you must also declare the "normal" size:

                    <Geometry>
                        <Size>
                            <Height>100</Height>
                            <Width>100</Width>
                        </Size>
                        <MinSize>
                            <Height>100</Height>
                            <Width>100</Width>
                        </MinSize>
                    </Geometry>
T
TooLzorAuthor
Known Participant
October 24, 2018

Wait...I've not had that in my manifest for like...a solid year if not more as it locks the size of the panel which is counter to a lot of the reactive size code I've got working in it.

That has in fact made it load, but yeah, now my panel is locked to whatever size data I put in there...

Any idea how I can have it resizeable like I've had it for a long time?

tomzag
tomzag
Inspiring
October 24, 2018

There was a bug with the geometry in CEP 8 which was now sorted out in CEP 9. That explains the (strange) behavior.

Simply also declare the MaxSize and your panel is resizable.

Size: The size your panel opens on the first opening

MinSize: The minimal size you can drag the panel

MaxSize: The maximal size you can drag the panel

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices