Well, you don’t say how you’re doing this, from svn or from the pre-built package, but I would start here
http://svn.modxcms.com/docs/display/revolution/MODx+Revolution and have a thorough read through the sections from this page, then try again.
Use MODx, or the cat gets it!
Ok guys, I’ve uninstalled my original SPForm from my test site and built/installed the new one, rev 375, all went without a hitch, no errors.
Configured it to use SMTP and no timers, worked like a charm, no probs here at all, but I did notice that it is now installed under /assets/components. Is this the preferred place to put all the modx-components now as opposed to assets/snippets ../templates etc.
Use MODx, or the cat gets it!
Quote from: shamblett at Dec 18, 2008, 03:06 AM
Ok guys, I’ve uninstalled my original SPForm from my test site and built/installed the new one, rev 375, all went without a hitch, no errors.
Configured it to use SMTP and no timers, worked like a charm, no probs here at all, but I did notice that it is now installed under /assets/components. Is this the preferred place to put all the modx-components now as opposed to assets/snippets ../templates etc.
Thanks for testing SPForm. The current version is (3.0.7) r379, which has a few bugfixes (I think captcha doesn’t work in your version). I haven’t been able to download SPForm from the WTF, did you try getting it there? For me, it looks like it’s downloading but never shows up on in core/packages or in the grid.
Also, Captcha 3.0.1 from the WTF won’t install for me. 3.0.2 from SVN works, though.
I’m not using the WTF site at the mo, I’m using the modx-components svn site, building the bits I need and doing a local install, this of course allows me to fix/tweak the code if I find errors and raise bugs etc. Is the stuff in the WTF site built from the components svn or somewhere else? I’m sort of assuming here that the components svn is the root of the components code, may be wrong here of course.
Use MODx, or the cat gets it!
OK guys, I’m working through assembling my Revo test site with the components from modx-components and filing bugs as I go, however I’ve noticed that some components e.g jot and docmanager for instance are quite broken/work in progress. Presumably you know about these or do you want bugs filing for them?
So far I’ve managed to install wayfinder, spform, breadcrumbs. ultimate parent and tinymce(ticket raised here) along with some templates I’ve packaged, so the site is basically useable.
Are there any plans to convert other big usage add-ons like maxi-gallery for instance?
Also, the description of adding pages to the manger to control 3rd party packages, i.e the new ’modules’ paradigm is OK if you want to do this interactively. Do you have any examples of how this can be packaged, i.e how do I create a ’top menu action’ for instance in a package build script.
Use MODx, or the cat gets it!
Ok OpenGeek,
Makes no sense to file bugs for things that aren’t released yet. We need developers working on these components actively, not describing the state of development in the bug tracker.
Ok, that’s sort of why I asked but what is released? What code baseline do we use? Have a quick look at this ticket
http://svn.modxcms.com/jira/browse/MODX-578. last comment entries. Whats is the difference between modx-components and WTF, I’m confused here at the mo. Previously in this thread I asked this and the reply was
All packages on WTF are built from modx-components, although the WTF packages may be a little out of date from the SVN, obviously.
. Assuming this is modx-components then is the best thing to do to pick a package, say Jot, fix it up then raise a single bug ticket with the changes etc attached?
It’s an object just like any other; you simply put the data into a vehicle according to how you want it to be installed
Yes, should have looked at the DB before asking this, the tables action,menus,contexts, context_reources etc. are used here presumably like any object.
Use MODx, or the cat gets it!
MODX Staff