5 Replies Latest reply on Jun 7, 2013 9:02 AM by Yogesh Upadhyay

    how to hide the sidekick dialog

    codonvirginia Level 1

      I want to hide the sidekick dialog on the publish page so when we click on the link they dont show the sidekick dialog anymore.

      Anyone know, can you help me out.

       

      Thanks,

       

      Jenny

        • 1. Re: how to hide the sidekick dialog
          orotas Level 4

          The sidekick should never show on a publish page. If sidekick is showing you probably installed your publish instances incorrectly. Check the run modes in your start script and make sure that only publish is listed as a runmode.

          • 2. Re: how to hide the sidekick dialog
            codonvirginia Level 1

            I check but I dont know why, can you help me. This is my start script. can you tell me which start file,  there are two start file, one is start and another is start.bat. These are infomation in start file.

            # TCP port used for stop and status scripts

            CQ_PORT=4505

             

            # HTTP host name

            CQ_HOST='abc.test.com'

             

            # interface that this server should listen to

            #CQ_INTERFACE='eth0'

             

            # runmode(s)

            CQ_RUNMODE='publish'

             

            # name of the jarfile

            #CQ_JARFILE=''

             

            # use jaas.config

            # CQ_USE_JAAS='true'

             

            # config for jaas

            CQ_JAAS_CONFIG='etc/jaas.config'

             

            # default JVM options

            CQ_JVM_OPTS='-server -Xmx2048m -XX:MaxPermSize=256M -Djava.awt.headless=true'

             

            # file size limit (ulimit)

            CQ_FILE_SIZE_LIMIT=8192

             

            # ------------------------------------------------------------------------------

            # do not configure below this point

            # ------------------------------------------------------------------------------

            if [ $CQ_FILE_SIZE_LIMIT ]; then

                    CURRENT_ULIMIT=`ulimit`

                    if [ $CURRENT_ULIMIT != "unlimited" ]; then

                            if [ $CURRENT_ULIMIT -lt $CQ_FILE_SIZE_LIMIT ]; then

                                    echo "ulimit ${CURRENT_ULIMIT} is too small (must be at least ${CQ_FILE_SIZE_LIMIT})"

                                    exit 1

                            fi

                    fi

            fi

             

            BIN_PATH=$(dirname $0)

            cd $BIN_PATH/..

            START_OPTS='start -c . -i launchpad'

            if [ $CQ_PORT ]; then

                    START_OPTS="${START_OPTS} -p ${CQ_PORT}"

            fi

            if [ $CQ_INTERFACE ]; then

                    START_OPTS="${START_OPTS} -a ${CQ_INTERFACE}"

            fi

            if [ $CQ_RUNMODE ]; then

                    START_OPTS="${START_OPTS} -Dsling.run.modes=${CQ_RUNMODE}"

            fi

            if [ $CQ_HOST ]; then

                START_OPTS="${START_OPTS} -Dorg.apache.felix.http.host=${CQ_HOST}"

            fi

            if [ $CQ_USE_JAAS ]; then

                START_OPTS="${START_OPTS} -Djava.security.auth.login.config=${CQ_JAAS_CONFIG}"

            fi

            if [ -z $CQ_JARFILE ]; then

                    CQ_JARFILE=`ls app/*.jar | head -1`

            fi

             

            java $CQ_JVM_OPTS -jar $CQ_JARFILE $START_OPTS &

                    echo $! > "conf/cq.pid"

            • 3. Re: how to hide the sidekick dialog
              sarwarbhuiyan Level 1

              Check the file name of the cq5 jar on publish. Also, did you copy any files from author to publish? Also, check sling.properties file if there is any run mode specified there.

              • 4. Re: how to hide the sidekick dialog
                codonvirginia Level 1

                the jar file is cq5-publish-4503.jar , I did not copy any files from author to publish, I build publish server .The sling.propertiies file are list below.

                 

                #Overlay properties for configuration

                #Fri Jun 07 07:28:44 EDT 2013

                sling.framework.install.incremental=true

                obr.repository.url=http\://sling.apache.org/obr/repository.xml

                org.osgi.framework.system.packages=${osgi-core-packages}, ${osgi-compendium-services}, org.apache.sling.launchpad.api;version\=1.1.0

                , ${jre-${java.specification.version}} ${org.apache.sling.launcher.system.packages}

                org.apache.sling.commons.log.file.number=5

                org.osgi.framework.startlevel.beginning=30

                org.osgi.framework.bundle.parent=framework

                gosh.home=${sling.home}

                org.apache.sling.commons.log.file.size='.'yyyy-MM-dd

                ds.factory.enabled=true

                repository.home=${sling.home}/repository

                sling.bootdelegation.sun.reflect=sun.reflect

                ds.loglevel=warn

                org.apache.sling.commons.log.julenabled=true

                org.osgi.framework.system.capabilities=${eecap-${java.specification.version}}

                osgi-compendium-services=org.osgi.util.tracker;version\="1.4"

                org.osgi.framework.storage=${sling.launchpad}/felix

                org.apache.sling.commons.log.file=${sling.home}/logs/error.log

                granite.product.version=5.5.0

                org.osgi.framework.bootdelegation=com.yourkit.*, ${org.apache.sling.launcher.bootdelegation}

                sling.fileinstall.dir=${sling.home}/install

                org.apache.felix.http.shared_servlet_context_attributes=true

                felix.startlevel.bundle=20

                sling.framework.install.startlevel=1

                sling.installer.dir=${sling.launchpad}/installer

                 

                Thanks,

                • 5. Re: how to hide the sidekick dialog
                  Yogesh Upadhyay Level 4

                  Add sling.run.modes=publish in your sling.properties and -Dsling.run.modes=publish as a JVM Param in your start script to see if that helps.

                   

                  To verify go to felix console and check if run mode is set correctly.

                   

                  Yogesh

                  www.wemblog.com