Announcement: New module Script Deploy

[uniqu3]

Hey cool
I had no Problems installing via downloaded files, didn't test MoMa.

In E_STRICT environment i see following

For SiteUtilities

Code: Select all

Strict Standards: Non-static method site_utils::getUserInfo() should not be called statically, assuming $this from incompatible context in D:\Localhost\www\demos\1.10.2\modules\SiteUtilities\lib\class.adminHeaderScripts_SU.php on line 61

For ScriptDeploy

Code: Select all

Strict Standards: Non-static method scriptdeploy_utils::_AdminCreateScriptList() should not be called statically, assuming $this from incompatible context in D:\Localhost\www\demos\1.10.2\modules\ScriptDeploy\admin\action.script_listings.php on line 24

Strict Standards: Non-static method scriptdeploy_utils::getScriptsList() should not be called statically, assuming $this from incompatible context in D:\Localhost\www\demos\1.10.2\modules\ScriptDeploy\admin\function.admin_scriptlist_tab.php on line 1

Strict Standards: Non-static method scriptdeploy_utils::is_editable() should not be called statically, assuming $this from incompatible context in D:\Localhost\www\demos\1.10.2\modules\ScriptDeploy\admin\function.admin_scriptlist_tab.php on line 1

Strict Standards: Non-static method scriptdeploy_utils::GetLastRevision() should not be called statically, assuming $this from incompatible context in D:\Localhost\www\demos\1.10.2\modules\ScriptDeploy\admin\function.admin_scriptlist_tab.php on line 1

Strict Standards: Non-static method scriptdeploy_utils::GetScriptGroupInfo() should not be called statically, assuming $this from incompatible context in D:\Localhost\www\demos\1.10.2\modules\ScriptDeploy\admin\function.admin_scriptlist_tab.php on line 1

Strict Standards: Non-static method scriptdeploy_utils::GetScriptGroups() should not be called statically, assuming $this from incompatible context in D:\Localhost\www\demos\1.10.2\modules\ScriptDeploy\lib\class.scriptdeploy_utils.php on line 1

Strict Standards: Non-static method scriptdeploy_utils::is_editable() should not be called statically, assuming $this from incompatible context in D:\Localhost\www\demos\1.10.2\modules\ScriptDeploy\admin\function.admin_scriptlist_tab.php on line 1

Frontend

Code: Select all

Strict Standards: Non-static method scriptdeploy_utils::Get_Notes() should not be called statically, assuming $this from incompatible context in D:\Localhost\www\demos\1.10.2\modules\ScriptDeploy\lib\class.scriptProcessing.php on line 1

And so on.

When Stylesheet (for example NCleanBlue) is saved with ScriptDeploy media="" is empty.

What is distracting, is that "preview" window can't be closed, or at least i can't see an option, or a option to set preview to "none" for example. (oh ok just found out it can be minimized by clicking on at bar on top)

Module editing Stuff is very cool but with heavy weight js usage, editing overall feels a bit sluggish like slow motion or like if i would of smoked something (you know that green stuff).

Great work, looking forward to the rest of the releases!!

[JeremyBASS]

I will retest.. I have been runing the module thru XDebug so it should have been caught. I'll look at it shortly.. Tk for reporting. -Jeremy.

[JeremyBASS]

@uniqu3 Ok, I have fixed the static notices. I forgot to set back to dev mode as I rushed it out after moving some places around as I'm on a different project .. I'll have the updated files tomorrow after I'm done with my project. Also RonnyK what you pointed out is updated. Thank you guys.
cheers -Jeremy

[Mieszko]

What is distracting, is that "preview" window can't be closed, or at least i can't see an option, or a option to set preview to "none" for example.

I agree. Would wish there were an option not to have that preview pop up all the time.

Nice module, nevertheless

[JeremyBASS]

I was going to add an "at will" opening of the preview, but since this is an unfunded mod that is only made for my needs and to speed my massive amount of sites I always keep the live preview window open. Till I get to the time when I can add the "at will" paths to control the preview windows you can always size the window down or dbl click the handle to minimize it. Hope that helps..

Cheers -Jeremy

[swgreed]

Hi Jeremy,

thanks for your fast reply!
The only issue during the upgrade: ScriptDeploy was not visible on the "Layout"-tab after upgrading, but "Deinstall/Install" on the "Modules"-tab fixed the issue.
The PayPal-Button on the ScriptDeploy module help page is broken.

I have several questions:
#1 Is it possible to turn the preview window off?

#2 When grouping CSS files, ScriptDeploy shows all available CSS-files that come with CMSMS by default and not just the ones that were created by ScriptDeploy. Due to the lack of a scrollbar while grouing the CSS-files it is impossible to reach entries further down (see screenshot attached)

#3 Is a special syntax necessary to lazy-load JS-grouped files or does e.g. {cms_module module=ScriptDeploy groupID="1" Stype="JS"} suffice?

Cheers

[JeremyBASS]

Hello swgreed,

#1 not yet. I know it's wanted but you can minimize it, or size it to any size. See since this is totally unfunded, so I try to get the nicety parts in but I work with the preview up as I go from templates to js to css and I make a site and this way I not need to go to a new tab. Speeds my work. But the option is planned on.

#2 I'll fix that... don't know where the scroll went

#3 it's {ScriptDeploy groupID="1" Stype="JS" defer=true} per the help. It was working last check but I don't defer "lazyload" javascript as after 100's of tests load js at the bottom of the html doc and using none dom forming javascript are still faster than a js with deferment.

I'm super under the gun so it'll be a day or so before I reload the new files. Sorry for the delay.

Cheers -Jeremy

[JimboDavies]

I've just tried to install ScriptDeploy and run into exactly the same problem as RonnyK.

SiteUtilities installs (or appears to) and ScriptDeploy then generates the same error:

Code: Select all

Fatal error: Class 'scriptdeploy_utils' not found in /home/stormforce23/stormforce.biz/modules/ScriptDeploy/action.defaultCSS.php on line 1

This then prevents me accessing the site or the admin console. I'm going to try uninstalling SiteUtilities, then doing a manual install of both.

[JimboDavies]

So, like RonnyK, I solved my install problem by installing siteutilities through the .xml file, followed by ScriptDeploy in the same way.

Module Manager definitely didn't like being left to it's own devices for the install!