0.9.6 Release Candidate Support

☆ A M B ☆
1,056 Posts

pixelchutes Reply #41, 19 years, 7 months ago

Quote from: OpenGeek at Feb 28, 2007, 07:53 PM

Unfortunately because that’s the version of the files in the distribution you unzipped. If you don’t want the latest snippets, you’ll need to restore the appropriate assets directories from your existing deployment.

This is one of the reasons I really hate having add-ons in the core distro, and another of the long list of motivations for a "pick and choose the add-ons you want" distribution, with much smarter installation and upgrade processes for the core and the add-ons you’ve chosen. This is definitely one of the central issues to be addressed immediately following 0.9.7 release, and I’ve been doing a lot of research into the best ways to accomplish it.

Ah, like MooTools... automated, user-defined packaging distros. I’ve scripted 7-Zip in a PHP online app before, I wonder if Third Party apps or just native OS functions are part of the MODx solution? I guess either/or, depending on benchmarking/required features...

Mike Reid - www.pixelchutes.com
MODx Ambassador / Contributor
[Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
________________________________
Where every pixel matters.

MODX Staff
10,725 Posts

opengeek Reply #42, 19 years, 7 months ago

Quote from: pixelchutes at Feb 28, 2007, 09:37 PM

Ah, like MooTools... automated, user-defined packaging distros. I’ve scripted 7-Zip in a PHP online app before, I wonder if Third Party apps or just native OS functions are part of the MODx solution? I guess either/or, depending on benchmarking/required features...

Yep, think MooTools meets the Eclipse IDE’s Configuration Manager and Find and Install features.

In developing a bootstrap installer prototype, we have found PHP libraries for zip and ftp that work even when the PHP support for those functions are not available. And we’ll have a fall-back to manual package extraction and/or delivery to the server in extreme cases.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

33 Posts

cliff_ie Reply #43, 19 years, 7 months ago

Quote from: desmortes at Feb 24, 2007, 06:04 AM

thanks to jeff.

have accomplish my issue, it was just a path mistake.

Thanks a lot for this team

Rock.

Could someone please tell me where to edit these "paths"? I’ve just installed TinyMCE 2.0.9 and as rock said before when I go to edit a page TinyMCE is not working - just getting code and it says TinyMCE underneath the editing panel in the dropdown.

Thanks, Cliff.

1,097 Posts

PaulGregory Reply #44, 19 years, 7 months ago

Minor HTML issue: the new upgrade-and-change-db option in the install uses the same ID as the main upgrade option, meaning that you cannot click on the bottom label to select that button. And probably makes that page invalid.

EDIT: Actually they do have different IDs but the labels don’t, so:

<label for="installmode2" class="nofloat">Upgrade Installation<br /><small>(edit database config)</small>

should be

<label for="installmode3" class="nofloat">Upgrade Installation<br /><small>(edit database config)</small>

No, I don't know what OpenGeek's saying half the time either.
MODx Documentation: The Wiki | My Wiki contributions | Main MODx Documentation
Forum: Where to post threads about add-ons | Forum Rules
Like MODx? donate (and/or share your resources)
Like me? See my Amazon wishlist
MODx "Most Promising CMS" - so appropriate!

78 Posts

tjalve Reply #45, 19 years, 7 months ago

I upgraded from 0.95 to rev 2425.

There appears to be a problem with QuickEdit - it don’t work.

Error console:

JavaScript - http://www.mydomain.tld/myMODx/
Event thread: load
Error:
name: ReferenceError
message: Statement on line 79: Reference to undefined variable: toolbar
Backtrace:
  Line 79 of linked script http://www.mydomain.tld/myMODx/assets/modules/quick_edit/javascript/QuickEdit.js
    this.toolbar.makeDraggable({handle : $E("h1", toolbar), onStart : (function ()
{
  this.toolbar.setStyle("opacity", 0.5);
}
).bind(this), onComplete : (function (x,y)
{
  this.toolbar.setStyle("opacity", 1);
  Cookie.set("QE_position", this.toolbar.getLeft() + "/" + this.toolbar.getTop(), {duration : this.cookieDuration});
}
).bind(this)});
  Line 46 of linked script http://www.mydomain.tld/myMODx/assets/modules/quick_edit/javascript/QuickEdit.js
    this.assignEffects();
  Line 1 of eval script 
    if (this.initialize && arguments[0] != "noinit")
    else
      Line 3 of inline#3 script in http://www.mydomain.tld/myMODx/
    qe = new QuickEdit(2, 1, "/myMODx/manager/", "assets/modules/quick_edit", $("QE_Toolbar"));
  At unknown location
    [statement source code not available]

QuickEdit headers:

<!-- Start QuickEdit headers -->
<script type="text/javascript" src="assets/modules/quick_edit/javascript/mootools.js"></script>
<script type="text/javascript" src="assets/modules/quick_edit/javascript/QuickEdit.js"></script>
<link type="text/css" rel="stylesheet" href="assets/modules/quick_edit/styles/toolbar.css" />
<script type="text/javascript">
 Window.addEvent('load',function() {
  qe = new QuickEdit(2,1,'/myMODx/manager/','assets/modules/quick_edit',$('QE_Toolbar'));
 });
</script>
<!-- End QuickEdit headers -->

So as I understand it, there are somethign wrong with the paths in this line:

qe = new QuickEdit(2, 1, "/myMODx/manager/", "assets/modules/quick_edit", $("QE_Toolbar"));

TJ

407 Posts

rasc Reply #46, 19 years, 7 months ago

Need fast help: upgraded from 0.9.5 to 0.9.6 rc1 and now TinyMCE doesn’t work. In global configuration TinyMCE always set to "simple". I can’t change this. In plugin configuration I can set all themes but nothing works. Editing a document doesn’t show me the TinyMCE. Switching in document editing window to FCKeditor also doesn’t have any effect. Any ideas? Found nothing in forum.

MODX Staff
12,272 Posts

Ryan Thrash Reply #47, 19 years, 7 months ago

Log out of your manager and re-run the installer in upgrade mode... and clear any site-related cookies.

Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me

407 Posts

rasc Reply #48, 19 years, 7 months ago

Will try this. Thanks for quick answer. In my opinion there are some problems with cookies regarding the whole system? (installation/upgrade issues, login, "remember me" function which doesn’t work furthermore at my system)

222 Posts

gadamiak Reply #49, 19 years, 7 months ago

Upgrade from 2066 (trunk), through 2409 (trunk) to 2428 (095dev branch).

QE doesn’t work in Opera 9.10/Win (both 2409 and 2428). QE bar is opaque and no drop down menus are available (someone mentioned that one before). It worked fine in 2066.

If during upgrade (2409 to 2428) the file manager path pointed to a location other than [tt]c:\path\to\modx\root\[/tt] (in Windows) the configuration screen shows errors about TinyMCE not able to find its files. It seems the path to [tt]assets/plugins/tinymce...[/tt] gets hardcoded somewhere during installation, as correcting the file manager path after the installation doesn’t help.

It seems that a TV of type ’image’ can’t contain a dot in the name. I changed my naming convention for TVs and chunks to use dots, and this has broken those of type ’image’. Simply the path doesn’t get saved and is reverted to the default value. I got the same behavior in 2409 and 2428.

This is the web: the only thing you know about who will come is that you don't know who will come.

☆ A M B ☆
1,056 Posts

pixelchutes Reply #50, 19 years, 7 months ago

Quote from: grad at Mar 06, 2007, 08:53 AM

Upgrade from 2066 (trunk), through 2409 (trunk) to 2428 (095dev branch).

QE doesn’t work in Opera 9.10/Win (both 2409 and 2428). QE bar is opaque and no drop down menus are available (someone mentioned that one before). It worked fine in 2066.

If during upgrade (2409 to 2428) the file manager path pointed to a location other than [tt]c:\path\to\modx\root\[/tt] (in Windows) the configuration screen shows errors about TinyMCE not able to find its files. It seems the path to [tt]assets/plugins/tinymce...[/tt] gets hardcoded somewhere during installation, as correcting the file manager path after the installation doesn’t help.

It seems that a TV of type ’image’ can’t contain a dot in the name. I changed my naming convention for TVs and chunks to use dots, and this has broken those of type ’image’. Simply the path doesn’t get saved and is reverted to the default value. I got the same behavior in 2409 and 2428.

I can likely confirm the TinyMCE issues. I had a local site (Windows/WAMP), created an .SQL dump/backup file, and pushed everything out to the hosting server...Ran the upgrades to most recent SVN.... Only now, I can’t get TinyMCE to load, portions of the manager error prematurely, etc. This is possibly related because my hosting server is a LAMP environment, and settings/paths all had to be updated accordingly.

Warning: include_once(/www/assets/plugins/tinymce/tinymce.lang.php) [function.include-once]: failed to open stream: No such file or directory in /www/manager/includes/document.parser.class.inc.php(724) : eval()’d code on line 12

...
(And many more errors like above related to TinyMCE failing file includes)

Weird. I kid you not, right after this post I tried (after many failed previous attempts) to edit a document, only now TinyMCE is loading fine, complete w/ attached styling etc??? Way too weird....I need to remember to log out of manager, clear site cookies, etc....THEN run the upgrade. Possible culprit?

UPDATE!

It turns out that siteCache.idx.php was my culprit. TinyMCE was still looking to the OLD (local/Windows) manager path, not the new UNIX path. Is there a way to Force-Update siteCache.idx.php ?

$c['filemanager_path'] = "C:/wamp/www/htdocs/mysite.com/";

Other Error:
As of rev 2446, and my upgrade/transfer process from above, I am getting frequent Incomplete Submissions when in the manager. Specifically, when trying to add a "Ditto" snippet that appears to have disappeared, or trying to Edit the QuickEdit Plugin, etc...I am thrown to my 404 error page from within the manager.

I can’t even re-add Ditto (via the GUI) because I keep getting 404 errors sad

I am not sure where to even look from here...

Hmm...I tried the following trick and Voila, problem solved...

.htaccess in /manager/

SecFilterEngine Off
RewriteEngine Off

Mike Reid - www.pixelchutes.com
MODx Ambassador / Contributor
[Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
________________________________
Where every pixel matters.