I’m up and running and tinkering around thanks to the patience of many people here!
But now I’m getting the following error:
MySource Warning
A HIPO Job with the same code name is currently being run by “Root User” (Id #5).
It was last updated at 13/12/2004 13:49:05
I don’t have anything locked for editing, I have even logged out of the admin interface, but each time I try to edit the one single page I have managed to create follwing the Quick Start Guide I get the message above after being redirected. (I also took out the DOCTYPE info incase that was what was causing the error)
I am wrestling with the very steep learning curve as it is and the Applet is so incredibly slow in Mozilla on the Mac so the interface is making my progress pretty hard going.
Any thoughts?
Thanks,
Matt
You'll have to log in as the root user, and go to the "HIPO Herder" screen, which you can get to through the orange icon in the top right of screen. Lock that, then tick all the boxes for hipos you know aren't running, and click commit. This will delete any dead hipos.
Sweet! Worked a treat. Thanks
…BUT you should see the WYSIWYG layout editor! I have a blur of buttons all over the screen. (I kept a screen snap if you want to see it, but I can't upload it)
I had to gently move my cursor around until I found "Enlarge Editor" and then it launches a window that works fine.
I was actually hoping to be able to edit the META data for this page from here. I'm not sure if that's even possible as I haven't read/figured out the manual yet.
Thanks,
Matt
Metadata has to be configured by creating a Metadata schema (from the Add menu in the Administration Interface) and then applying that schema to the assets to which you wish to apply the metadata.
Once you've done that, you need to ensure that your design has a metadata design area, so that Matrix knows where to print the metadata values that you entered.
Aaargh! I just replied in detail to your other problem... you could have given a thumbs up back there... although I note now that if you are up and running using the instructions that came before mine, you will be using pear under one version of PHP, but actually serving it via another. Which is a little... odd.
Anyway
That problem with the editing screen came up for me too on OS X browsers, is fine in the admin interface though, just happens in the "in-place" edit screens (accessed via "/_edit").
Maybe it's a bug we can report???
Do you guys 'do' Mac client bugs???
BTW, firefox is a lot faster than mozilla, and should work fine. I even got Safari to work without any hassle using the JavaPlugin from sourceforge and it's a little faster again.
Yes, we do Mac support. The problem with the editing screen is usually to do with the inclusion of a <!DOCTYPE …> declaration in the frontend design. The version of the editor in the MySource Matrix v3.2 release was not XHTML compliant and when a browser goes into "proper" XHTML mode, it screws up. We have already fixed this in the current development version.
Safari should run the Java applet natively (i.e. without any plugins), but as Safari doesn't support editable regions, the WYSIWYG editor is unusable. We recommend the use of Firefox and the Java Embedding Plugin for the most user friendly and stable editing interface on MacOS X.
You are right and right again…
Removing the <!DOCTYPE> declaration fixed it and also took out the xml attribute in the <html> tag fixed the editor.
That one comes up more and more often the more we move to xhtml…
Safari isn't playing nice with the HTMLarea plugin… time to bug Apple for support in Safari.
OK, I have set up one page, I have made sure there are no HIPO's running around in the paddock and I have gone over to a PC running Windows XP and tried to log on to try _edit
I had to log on using my root password (not sure why) to even see the page, but when I enter _edit
but I get a redirect:
?sq_redirect_url=%2F%7Ematt%2Fmysource_matrix_3-2-0%2F_edit%2F
and no WYSIWYG interface?
I am really sorry to be asking lots of stupid questions, but my next questions will be about meta adta/schema:
Do I have to code in every one I want to use in the schema? Isn't there some way I can download/embed them from somewhere? If I want to use Dublic Core - so what is the best way to code in DC.Title, DC.Description etc so that users can enter this info when they edit a page?
In the manual this section looks great - how can i get my empty schema to come up like that without spending 5 hours coding each one? (And where can I find the keyword shortcuts for these? The keyword shortcuts in the manual are all about last modified and asset URL)
Anyway, back to other work! (I'm enjoying the learning curve, its just left me a bit overwhelmed)
"Remember Kids, There are no stupid questions, only stupid people"
South Park - Mr Garrison, 4th Grade Teacher.
For metadata, you have to spend the time creating the schema yourself.
Once you create the strucutre of the schema, you can go through and enter default values and set some elements to be non-editable. If you go to the details screen of a metadata text field, you'll see a link to open the keyword popup.
Also, you should be doing all this work in the Administration Interface (/_admin). The /_edit interface on a freshly installed system is quite limited until its configured.
Well I'm back at work for 2005 and I've been asked to look at MySource again. In my last post I mentioned that the WYSIWYG editor looks terrible in Firefox on the mac. The layout is all over the place. When entering edit mode the buttons cover the whole page. I have a screen snap, but there isn't a way to post it here.
Any tips as to why this is laying out so badly? Have any other users come across this? Is it related to other problems I am having?
Thanks,
Matt
Is this in the Administration Interface (/_admin), or via the Simple Edit Interface (/_edit)?
its in /edit
more than happy to post a screen snap - looks freaky!
Heh, its a known problem with v3.2.1 – the WYSIWYG Editor in that version is not XHTML compliant, and if your design forces XHTML (using a DOCTYPE declaration), the editor will break. Either remove the DOCTYPE declaration (to make the browser use quirks mode) or wait for v3.4 when the editor is fixed.
Just a note that it is also fixed in the current beta version (3.3.1) on the web site.