Easy Edit Suite installation questions

jeffers · 2012-04-18 10:21:18 UTC

Hi All and apologies if this has already been answered elsewhere (I have searched first before posting).

I am evaluating squiz along with several other open source cms products as a replacement for Cardiff University's (UK) current web cms. I am following the instructions in the installation guide (http://manuals.matrix.squizsuite.net/__documents/ees-installation-guide.pdf) and have 2 questions:

I have created a Cardiff University design in the designs folder and set up all the files and URLs required by the installation guide

Q1. I am trying to use the example static html as referenced in the help manual (http://manuals.matrix.squizsuite.net/designs/appendices/appendix-example-static-html-file). Does this file have to be merged with the parse file as created from the ees installation guide?

Q2. Where can I download the associated files for the example static html (css, js etc…)?

Many thanks,

Jeff.

shall · 2012-04-18 11:18:16 UTC

Hey Jeff

I would focus on first getting a site up and running with a design file before adding EES. Sounds like you need help with that bit, is that correct?

What version of matrix do you have, and are you using one of the VM downloads from the squiz suite site?

Cheers

Scotty

jeffers · 2012-04-18 11:36:46 UTC

Hi Scotty,

Thanks for the reply. I have the latest demo VM. I will try what you suggest first (stripping outthe ees stuff and getting a simple design working first).

Thanks.

jeffers · 2012-04-18 12:45:20 UTC

I now have a design template which is displaying in university colours and is displaying the actual content from the database using the following…

[xml]<h1><MySource_PRINT var="asset_name" /></h1>

<MySource_AREA id_name="page_body" design_area="body" />[/xml]

The question now is - how do I modify that to use the easy edit suite (which is what will sell squiz matrix to the majority of our users)? I have already done the installation and set all the correct permissions and URLs - I just need to know where to place the easy edit stuff in this new template.

Cheers.

jeffers · 2012-04-18 13:29:11 UTC

I have gone back into the parse file and added the easy edit suite specific lines above the <!DOCTYPE html> entry. I think it has worked as it now fails on the version of jquery 1.6.2 Can I update that in the VM do you know?

shall · 2012-04-18 15:33:40 UTC

Hey Jeff

Have you followed the steps to the letter on http://manuals.matrix.squizsuite.net/ees/chapters/installation ? I noticed you posted a link to the old PDF archived install process. If you have a new VM you should be using the details directly from that installation page not the PDF download.

Also, have you installed the ees folder into the correct location server side?

Feel free to post some screenshots of any issues you are seeing.

Cheers

Scotty

jeffers · 2012-04-19 08:37:02 UTC

Thanks Scotty,

I am running back through the instructions on the manual page you indicated to check that my setup is the same. things:

The guide says "To setup the Easy Edit Suite on a Site, an EES Styles and Scripts Standard Page must now be created". Is there any particular location where this standard page should be created?

Cheers,

Jeff.

shall · 2012-04-19 09:30:45 UTC

Nope, although best to keep close to your designs, we normally create a 'Nested Helpers' folder somewhere close by which contains assets like these which are essentially used as global 'includes' (for lack of a better comparison) for designs and because the ees styles and scripts standard page is used in this manner it doesn't need a URL, so you could easily put it outside the designs folder and at the root somewhere, only asset kept under the designs folder, media folder, users folder, web services folder, and site assets have web paths.

jeffers · 2012-04-19 09:41:13 UTC

Thanks,

I'm nearly there I think.

I have now done as far as this…

Edit the URL under the heading Squiz Matrix / Easy Edit JS API. Ensure this path matches the location of the JS API asset you created earlier.

Edit the URL under the heading Easy Edit Configuration. Ensure this path matches the location of your EES configuration file asset.

But for the life of me I can't see where the next bit is done..

# On the Details screen of the base level (direct children) Customisation(s) of your Site's Design, customise the nested_ees_code design area.
# On the Details screen of the customised design area, select the EES Styles and Scripts Standard Page asset in the Nested Asset field.

I created a new customisation on my design called "nested_EES_code" but when I look at its Details screen I see no Nested Asset Field.

Jeff.

shall · 2012-04-19 11:28:05 UTC

Hey Jeff

Wow, you're really going well considering your giving yourself squiz matrix design 101 on the process, champion effort.

You probably would (or should have) gone through the following process to create your design customisation…

1 - right clicked on design file and selected 'customisations' screen'

2 - aqcuired locks on customisation screen, checked the new customisation tickbox, and given it a name and saved

3 - click the new customisation that would have appeared under 'current customisations'after save

4 - acquired locks

5 - selected the tickbox next to 'nested_ees_code' under the 'uncustomised' section and saved

6 - This next part is the way to get to a customisation screen… click on the new customised design area that would have appeared under 'customised' section after save, this should look like a hyperlink for the word 'nested_ees_content'

7 - boom! this is considered the details screen of a customisation… bit of a tricky one actually

8 - acquire the locks and DONT change anything under 'general' section, the design automatically prints this within the exit design area

9 - under the 'link' section click on 'change' and select your standard page that should be set to raw html with all the ees goodness inside of it

10 - if you havnt set a standard page to raw html you need to right click on it, select edit contents, and then click on the little orange 'p' properties icon, select raw html from 'presentation' drop down and raw html from 'content type' drop down, save changes. If you dont do both of these you'll find a bunch of extra html tags will be dumped inside of the head tag that all the ees code goes into which is bad joo joo

shall · 2012-04-19 11:34:00 UTC

I will look into whether we can change wording for the manuals, the way you can get back to step 6 is to expand your design tree in the asset map and right click on the new customisation and select 'details'.

By the way, dont forget to apply this new customisation to the site asset you are using so it inherits these changes… right click on site asset, settings, acuire locks, select 'change' from 'system defined font end design' and point to new customisation, any asset under your site (that dont have designs settings of their own) will auto inherit this.

jeffers · 2012-04-19 12:04:49 UTC

I knew it would be something simple! I just didn't spot that I had to tick a checkbox and commit

I have completed it all now and added the custom login - unfortunately I now login to a completely blank screen; though the following appears in the page source…







<title>Loading Easy Edit Suite…</title>



I'm going to go through the install instructions again (I wonder if I have missed a permissions setting somewhere).

Very grateful for all your help.

Jeff.

jeffers · 2012-04-19 12:17:00 UTC

Is there any significance to the fact that the manual tells you to install ees to:

home/websites/matrix/data/public

but the code pasted into the Raw HTML field of the EES Styles and Scripts asset references:

/__data/ees/etc…/etc…

?

Jeff.

shall · 2012-04-19 15:08:18 UTC

I would assume you are using the URL applied to the demo VM, which you probably applied to the site asset? So you should be able to view your site in EES at http://matrixdemo.squiz.net/_edit - if so then the manuals example of /__data/ees/blah will point all of the ees file references to public data directory within the main matrix install folder. It would be a matter of dropping the ees folder directly into the public data directory. In firebug console or nettab are you seeing red 404's for ees files?

shall · 2012-04-19 15:18:42 UTC

Could you post a text file version of what you have in your designs file at the moment, and also a text file version of view source once you are logged into edit mode?

jeffers · 2012-04-19 15:30:25 UTC

Hi,

I am using devsquiz.cf.ac.uk/publicsite/index/_edit so I have…

http://devsquiz.cf.ac.uk/_web_services/easy-edit-suite.js

http://devsquiz.cf.ac.uk/_media/EasyEditConfigSample.js

http://devsquiz.cf.ac.uk/_designs/cardiff-university

ees-styles-scripts-nested-standard-page

I will post the text files tomorrow morning (hometime here in the UK

Many thanks,

Jeff.

jeffers · 2012-04-19 15:31:52 UTC

Page source…

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">

<head>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />







<title>Loading Easy Edit Suite…</title>



<!–

Running Squiz Matrix

Developed by Squiz - http://www.squiz.net

MySource, MySource Matrix and Squiz.net are registered Trademarks of Squiz Pty Ltd

Page generated: 20 April 2012 01:30:31

–>

<link rel="stylesheet" type="text/css" href="http://devsquiz.cf.ac.uk/__lib/web/css/limbo.css" />

<script type="text/javascript" src="http://devsquiz.cf.ac.uk/__lib/js/translation.js"></script>

<script type="text/javascript" src="http://devsquiz.cf.ac.uk/__data/system/core/js_strings.en.js"></script>

<script type="text/javascript" src="http://devsquiz.cf.ac.uk/__lib/html_form/html_form.js"></script>

<script type="text/javascript" src="http://devsquiz.cf.ac.uk/__lib/js/general.js"></script>

<script type="text/javascript" src="http://devsquiz.cf.ac.uk/__lib/js/debug.js"></script>

<script type="text/javascript" src="http://devsquiz.cf.ac.uk/__lib/js/edit.js"></script>

<script type="text/javascript" src="http://devsquiz.cf.ac.uk/__lib/js/tooltip.js"></script>

<script type="text/javascript"><!–

//<![CDATA[

// slip our own onLoad function into the onLoad event of the window

var SQ_DOCUMENT_LOADED = false;

function page_on_load()

{

// let everyone know the document is loaded

SQ_DOCUMENT_LOADED = true;

}// end page_on_load()

function print_tooltip()

{

if (window.self.name == 'sq_main') {

tooltip.print();

}

}

var SQ_FORM_SUBMITTED = false;

function form_on_submit()

{

if (SQ_FORM_SUBMITTED) {

alert(js_translate('form_already_submitted'));

return;

}

// basically if they get this far then we can submit

SQ_FORM_SUBMITTED = true;

return true;

}//end form_on_submit()

//]]> -->

</script>

</head>

<body>

</body>

</html>

shall · 2012-04-19 15:40:55 UTC

Hey Jeff

Based on view source results looks like the customisation isnt printing the nested page contents into the head there, should be directly under the comments that mention it.

Considering your doing a basic evaluation of the product, throw me the design file contents in a text file and ill spend a few moments changing it so you dont need the customisation and nested page bit just so you can get it running.

Cheers

Scotty

jeffers · 2012-04-20 07:39:19 UTC

Thanks Scotty (the evaluation scoresheet includes support - so you're scoring well there )

Here's the design file (minus our static html)…

[xml]

<MySource_AREA id_name="exit_area" design_area="exit" print="no"></MySource_AREA>

<MySource_AREA id_name="nested_EES_code" design_area="nest_content" print="no" />

<MySource_AREA id_name="simple_edit_EES" design_area="show_if">

<MySource_SET name="condition" value="simple_edit_mode" />

<MySource_THEN>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">

<head>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />







<title>Loading Easy Edit Suite…</title>



<MySource_PRINT id_name="nested_EES_code" />

</head>

<body></body>

</html>

<MySource_PRINT id_name="exit_area" />

</MySource_THEN>

</MySource_AREA>

[/xml]

shall · 2012-04-20 16:33:31 UTC

Hey Jeff

Because your just trying to get this cranking we'll avoid the best practise approach of using the nested page, which is just a way of being able to re-use stuff acroos multiple design files.

Replace the code example you gave me with the following…

[xml]

<MySource_AREA id_name="exit_area" design_area="exit" print="no"></MySource_AREA>

<MySource_AREA id_name="nested_EES_code" design_area="nest_content" print="no" />

<MySource_AREA id_name="simple_edit_EES" design_area="show_if">

<MySource_SET name="condition" value="simple_edit_mode" />

<MySource_THEN>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">

<head>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />







<title>Loading Easy Edit Suite…</title>



<link href="/__data/ees/easyedit.min.css" rel="stylesheet" type="text/css" media="screen" />





<script type="text/javascript" src="/_web_services/xxxx.js"></script>



<script type="text/javascript" src="/__data/ees/Libs/jquery/jquery-1.6.2.min.js"></script>

<script type="text/javascript" src="/__data/ees/Libs/jquery/ui-1.8/ui.custom.min.js"></script>

<script type="text/javascript" src="/__data/ees/Libs/jquery/jquery-ellipses.js"></script>

<script type="text/javascript" src="/__data/ees/Libs/jquery/validate-1.6.0/jquery.validate.min.js"></script>

<script type="text/javascript" src="/__data/ees/Libs/jquery/jquery.ba-bbq.min.js"></script>





<script type="text/javascript" src="/_media/xxxx.js"></script>



<script type="text/javascript" src="/__data/ees/easyedit.min.js"></script>

</head>

<body></body>

</html>

<MySource_PRINT id_name="exit_area" />

</MySource_THEN>

</MySource_AREA>

[/xml]

Once you have replaced and saved then

Replace the JS api web path in the above example with the once for your JS API (this is a step in the manuals) just locate your js api in the asset map and right click on it, select web paths screen, and copy the web path you see there and replace in design file. The one you have to replace above is… /_web_services/xxxx.js
Do the same thing for the EES configuration file that you would have created, the one that you need to replace above is … /_media/xxxx.js
Once saved, make sure your test site asset is using the design file instead of any customisations you may have created, do this by right clicking on site asset, select settings, then change the front end system design setting to point to your test design file
Preview your site, append with /_edit and lets see if things get better

Cheers

Scotty