Quote from: OpenGeek at Jul 01, 2005, 12:07 PM
This was an upgrade, just FYI -- and though the FCKeditor files were in the plugins directory, they just didn’t show up in the settings...
Ok, I have not tested with an update as yet but did the manual fix work for you?
I was asked to take this over here.
after checking my session files and all the other goodies that come with sessions I believe that there is actually a bug in the install.
On about line 14 there is
// session loop-back tester
if(!isset($_GET[’s’])) {
$_SESSION[’session_test’] = 1;
// I had some problems with sessions when I used headers. This works ok
echo "<html><head><title>Loading...</title><script>window.location.href=’".$_SERVER[’PHP_SELF’]."?s=set’;</script></head><body></body></html>";
exit;
}
I think it should be
// session loop-back tester
$_SESSION[’session_test’] = 1;
if(!isset($_GET[’s’])) {
// I had some problems with sessions when I used headers. This works ok
echo "<html><head><title>Loading...</title><script>window.location.href=’".$_SERVER[’PHP_SELF’]."?s=set’;</script></head><body></body></html>";
exit;
}
because on line 317
// check sessions
echo "<p>Checking if sessions are properly configured: ";
if($_SESSION[’session_test’]!=1 ) {
echo "<span class=’notok’>Failed!</span></p>";
$errors += 1;
} else {
echo "<span class=’ok’>OK!</span></p>";
}
that is where it fails.
At lease this worked for me.
wizdom’s answer was
Strider,
by moving the $_SESSION[’session_test’] = 1 line above the if block you make the session test useless.
The statement $_SESSION[’session_test’] = 1 will allways set the session_test variable to 1 and it will allways pass even when the session does not exists
which really isn’t true. The only thing that if block tests is if the if(!isset($_GET) works. Setting it above tests sessions out. But for some reason I have noticed isset’s when running apache 2 with php 4.3.11 on a 2000 machine sometimes acts funny.
Apache/2.0.53 (Win32) mod_ssl/2.0.53 OpenSSL/0.9.7c PHP/4.3.11 mysql/ 3.23.49
which should answer rthrash’s question after wizdoms answer.
I have tested it out on a "real" server and it works fine.
but besides this ... This is a really nice cms.
one question I have though is why did you do the etomite=modx=blahblah .. was it for backward compatibility with etomite snippets?
-
MODX Staff
- 12,272 Posts
Howdy neighbor (Strider=Jason=lives 30 minutes away from me),
$etomite = $modx = blah is for backwards compatibility. Snippets and chunks written for Etomite (from whence we sprang...) should run without modification in MODx.
Although the reverse doesn’t necessarily apply. You might want to upgrade your MySQL to 4.0.x or 4.1.x, as we’ve seen some goofiness on occassion with the 3.x series, although I don’t see how that would affect the sessions as I don’t recall of the top of my head if thy’re in the DB or not... hmmm...
Thanks for the feedback and keep it coming! If Raymond survives Hurricane Dennis with power (he’s in Kingston, Jamaica) then we should see a lot of commits? of the new content type stuff soon and be very close to a Tech Preview 3 release which will represent the turn towards home and our 1.0 release and re-branding.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
Hi All,
We made it I’m back now. Lot’s of great things to come. TP3 has over 15 new features to say the least.
Strider,
Thanks for the fix. I’ll take a look at it as soon as I get a few other things ironed out and then commit to my branch
Hello Everyone,
I’ve just uploaded the latest stuff I’ve been working on inside SVN (raymond). Here are some of the changes made since jun 30:
* remove manager/dynamic/mutate_personal_prefs.dynamic.action.php
* add recursive parsing using $minParserPasses and $maxParserPasses options. Defaults to 10 passes
* enable cached documents to support web user security.
* modify parser to recreate the documentObject for cached documents.
* change variable $snippetParsePasses to $minParserPasses, $maxParserPasses and remove $nonCachedSnippetParsePasses from documentparser class.
* rename mergeHTMLSnippetsContent to mergeChunkContent
* retain modified values during postbacks for documents, users and web users
* remove 11.php and 4.php
* rename frame 5.php to scripter.php ans 12.php to topbar.php
* rename frames 8.php, 2.php and f3nav.php to l0mnu.php, l1mnu.php and l2mnu.php respectively - this is to make it easier to locate menus frames
* move user_management.dynamic.action.php and web_user_management.dynamic.action.php to static folder
* prevent users from changing user id when editing a manager or web user
* add OnManagerPageInit,OnWebPageInit event
* add content disposition to documents
* add custom content-types
* add blank template feature to document
* add site unavailable (offline) page
* remove manager/media/fckeditor (TP2 only)
* remove manager/media/tinymce
* fix friendly aliases and url with prefixs
* strip aliases of special characters (e.g. % ’ $ * & !, etc)
* automatically check for duplicate document aliases
* have menu indexes at the same level increment automatically.
* add support "override" file feature. This will allow developers to override the support.inc.php by adding an override.support.inc.php file inside the manager/includes folder
So far I’ve tried upgrading from TP2.1 without any problems but that’s on my PC. You guys will have to test both new install and upgrades on Etomite 0.6 and MODx TP2.1
Also remember to test the new features such as custom content types, web user security with cached and uncached documents, etc
Overal I think TP3 is much more secure and stable. for example, users will not be able to view you cached documents or system configuration settings from the web as with previous versions. This is due to the .php extension that was added to the siteCache.idx and doc{id}.pagecahe files
Let me know what you think of it.
I think the this line inside index.php is triggering notices:
error_reporting(E_ALL);
I think by setting this to error_reporting(E_ALL ^ E_NOTICE); should ignore notices
You can solve this by adding this line above line 1862 in document.parser.class.inc.php
if(!isset($this->pluginEvent[$evtName])) return false;
Let me know if it works.
MODX Staff