-
-
- 9 Posts Send PM
Jack_hawk Reply #31, 3 years, 1 month agoBut did you try MODx Revolution? In posting #23 you spoke of MODx 1.0.2.
as I mentioned earlier, I'm not familiar with modx and its names.
Well, "revolution" is 2.0.0 beta.
I see two distributions are available - advanced and regular. Which one do use?
Release Date: March 23rd, 2010
This is the advanced download of MODx Revolution 2.0.0-rc-1 Advanced.
Release Date: March 23rd, 2010
This is the traditional download of MODx Revolution 2.0.0-rc-1. -
-
-
- 142 Posts Send PM
enigmatic_user Reply #32, 3 years, 1 month agoQuote from: Jack_hawk at Mar 30, 2010, 02:14 AM
Please take a look at the screenshot I provided in posting #22. It's 3.8.12.
Jan, I still see no info from you about your version of the debugger. Is it 3.8.0, 3.8.1, or 3.8.2?
Quote from: Jack_hawk at Mar 30, 2010, 02:14 AM
As I said, at the moment I don't have the time to play around with PHP installations. No, I did not try PHP 5.3.2. But even if PHP 5.3.1 is buggy, the debugger should try to cope with it. I use a debugger to debug things running on the current PHP version, not a PHP version to run a debugger.
This suggests you're using php 5.3.1. Did you try php-5.3.2?
Quote from: Jack_hawk at Mar 30, 2010, 02:14 AM
Oh, well, come on. I had to tell you numerous times where to find the things that I already wrote down in this thread and that I had to repeat for you, but I stayed polite, so please do so, too.
Did I say anything like this? If you read my post
Quote from: Jack_hawk at Mar 30, 2010, 02:14 AM
That's right - I meant PHP modules (I don't have much time today, so I mixed this up in my hurry).
you'll see that I didn't mention Apache modules at all.
Quote from: Jack_hawk at Mar 30, 2010, 02:14 AM
I don't have any other problems with XAMPP, and as I said, I'm not new to PHP. As a matter of fact, I'm a developer for quite some years now. I activated those Apache and PHP modules etc. that I need and deactivated those that I don't need.
You're using XAMPP it's full of stuff that you don't really need and that's what do crash apache+php.
Quote from: Jack_hawk at Mar 30, 2010, 02:14 AM
Maybe I'm not quite the noob you seem to think. And by the way: I don't have a brother.
[q]But that doesn't mean that DBG couldn't be the culprit[/q]
Oh well, if your brother came into the room when Apache crashed, does it mean your brother is a culprit?
TWO DIFFERET DEBUGGERS were tried and it's alone is a strong evidence to believe they are not the problem.
Two different debuggers crashed when MODx Revolution was used, and they didn't crash when using other scripts. PHP 5.3 is quite new, so maybe both debuggers might have problems with something that's new in PHP 5.3 and that is seldom used. And I just said 'it crashes when...' - I did not even name a culprit. So please don't get funny.
Quote from: Jack_hawk at Mar 30, 2010, 02:14 AM
Okay, I'm asking you a last (third) time: Did you use MODx Evolution or Revolution in your tests?
Also
I installed two configurations - apache+php and iis+php. Neither crashed modx.
Oh, you posted while I answered your posting. Just a moment...
Quote from: Jack_hawk at Mar 30, 2010, 02:34 AM
There's a Release Candidate now.
as I mentioned earlier, I'm not familiar with modx and its names.
Well, "revolution" is 2.0.0 beta.
Quote from: Jack_hawk at Mar 30, 2010, 02:34 AM
The 'regular' one should be fine. But there should only be a difference regarding the installation method. Myself, I'm using the SVN version. You'll find some hints for using it here.
I see two distributions are available - advanced and regular. Which one do use?
Quote from: Jack_hawk at Mar 30, 2010, 02:29 AM
Just use the 'Quote' button at the lower right of a posting to answer. Or the quote button of the editor while answering (earth icon). Or the 'Insert Quote' link at the upper right of a posting while answering. BBCode is supported, too:
btw seems this forum board does not support bbcodes.
how do you quote?
[quote]Text[/quote]
Cheers,
JanThis message has been ROT-13 encrypted twice for higher security. -
-
-
- 9 Posts Send PM
Jack_hawk Reply #33, 3 years, 1 month agoAs I said, at the moment I don't have the time to play around with PHP installations. No, I did not try PHP 5.3.2. But even if PHP 5.3.1 is buggy, the debugger should try to cope with it.
To me it's clear that the things do not work in this way. For example, you just can't expect an application to be stable under unstable OS. What you'd expect and may request for is a stable application under stable OS. You can't request from an application to make your OS stable.
Similarly, with php, php application, and debugger the relationship between them looks like below, and you can't expect any debugger or php application to be stable under unstable php and you can't request them to make your php stable (or cope with it):
[apache]
|
+--[php]--
|-[debugger]
|
+- [php application]
If php is unstable you can't expect anything below to work stable.
I'd highly recommend you to update php to standard version. First determine whether xamp's Apache binary is vc6 or vc9. Try to find msvcr word in the exe. If found word is msvcrt.dll, it's vc6. If it's msvcr90.dll, the binary is vc9. Then download appropriate php zip archive from http://windows.php.net/download/
It should be http://windows.php.net/downloads/releases/php-5.3.2-Win32-VC9-x86.zip (vc9) or http://windows.php.net/downloads/releases/php-5.3.2-Win32-VC6-x86.zip for vc6.
then stop apache, remove (or rename) xampp/apache/bin/php.ini file and xampp/php directory.
Then unpack php archive into fresh xampp/php/ directory, rename xampp/php/php.ini-development to
xampp/php/php.ini, uncomment session.save_path in php.ini and make it pointing to windows TEMP directory,
uncomment extension_dir and make it pointing to path/to/xampp/php/ext/, uncomment mysql php extension.
add zend_extension=/path/to/debugger, and finally copy php.ini to xampp/apache/bin/.
Run apache and check phpinfo()
Basicly, that's all steps and they would not require more than 2minutes
-jack -
-
-
- 9 Posts Send PM
Jack_hawk Reply #34, 3 years, 1 month agoTwo different debuggers crashed when MODx Revolution was used, and they didn't crash when using other scripts.
Only crash proves. If in some cases you didn't see crashes, it does not prove anything.
For example, suppose you worked with debugger and application under a perfectly stable php, then switched to XAMPP and got these crashes, wouldn't you blame at XAMPP? -
-
-
- 142 Posts Send PM
enigmatic_user Reply #35, 3 years, 1 month agoQuote from: Jack_hawk at Mar 30, 2010, 03:46 AM
Well, Windows, Apache, PHP and MODx as a whole work just fine. I guess it should be possible to create a debugger DLL that doesn't cause crashes even if there are some bugs in the other components, shouldn't it? The debugger is not even used, the DLL is just linked in via the php.ini.
Similarly, with php, php application, and debugger the relationship between them looks like below, and you can't expect any debugger or php application to be stable under unstable php and you can't request them to make your php stable (or cope with it):
[apache]
|
+--[php]--
|-[debugger]
|
+- [php application]
If php is unstable you can't expect anything below to work stable.
Also, I'm not sure what you're trying to convince me of. I never said that DBG is evil and I just stated what is happening when I'm doing this or that. I even repeated this especially for you in my last posting. I posted here just because someone had a similar problem. I really don't know why you don't even take into consideration that there could be a problem with DBG. Are you the NuSphere employee who deleted my posting in the NuSphere forum that pointed to this thread?
BTW: Did you ever hear of Occam's Razor?
Quote from: Jack_hawk at Mar 30, 2010, 03:46 AM
Did you try out MODx Revolution in the meantime? That would not require more than 2 minutes.
Basicly, that's all steps and they would not require more than 2minutes
Quote from: Jack_hawk at Mar 30, 2010, 03:59 AM
Oh come on, please accept that you aren't the only one who knows how to turn on a computer...
Only crash proves. If in some cases you didn't see crashes, it does not prove anything.
I really appreciate your attempts to help me, but if you have something more important to do, please feel free to do that. I don't have an urgent problem - deactivating MODx's custom session handling solves all my problems, and I can work with my development server just as I intend to do.
Cheers,
JanThis message has been ROT-13 encrypted twice for higher security. -
-
-
- 14,470 Posts Send PM
One of the things I like best about the MODx community and its Forums is that, unlike some other places, people attack problems here rather than each other.
We're really all on the same team -- us against the problems we all face. Attacking each other hurts everyone, wastes time and resources, and ultimately hurts the whole community by driving off people who might help us.
MODX info for everyone: http://bobsguides.com/MODx.html -
-
-
- 142 Posts Send PM
enigmatic_user Reply #37, 3 years, 1 month agoQuote from: BobRay at Mar 30, 2010, 12:00 PM
That's what I hoped, too.
One of the things I like best about the MODx community and its Forums is that, unlike some other places, people attack problems here rather than each other.
I'm sorry that I'm not as calm and relaxed as I should be when I feel provoked... 
Cheers,
JanThis message has been ROT-13 encrypted twice for higher security. -
-
-
- 964 Posts Send PM
charliez Reply #38, 3 years, 1 month agoDont worry, you will get the MODx Zen when you get to 50 posts
Website: www.mercologia.com
MODX Revo Tutorials: www.modxperience.com
MODX Professional Partner -
-
-
- 14,470 Posts Send PM
LOL.
Meanwhile, let me re-ask my dumb question:
How do you debug within MODx? I've used PhpED to debug snippet code running outside of MODx, but never within it.
Executing /index.php gives me the home page, but any link gives a 404 error.
Executing /manager/index.php gives me the login page, then a 404 error.
What's the secret?
MODX info for everyone: http://bobsguides.com/MODx.html -
-
-
- 142 Posts Send PM
enigmatic_user Reply #40, 3 years, 1 month agoQuote from: charliez at Mar 30, 2010, 12:38 PM
Great, that's what I waited for all my life!
Dont worry, you will get the MODx Zen when you get to 50 posts
The 9,900+ posts in the forum of my web hoster don't seem to be very helpful...
Quote from: BobRay at Mar 30, 2010, 12:50 PM
Which debugger do you use? I guess it's PhpED's DBG (because of your posting #12), but I'm not totally sure.
How do you debug within MODx? I've used PhpED to debug snippet code running outside of MODx, but never within it.
Executing /index.php gives me the home page, but any link gives a 404 error.
Executing /manager/index.php gives me the login page, then a 404 error.
I put the code of those snippets that are a little bit more complex (read: that are longer than just a few lines) into separate files and just include them in the snippet itself. Then you can add the line
DebugBreak();
where you would like the execution to halt just as if you entered a breakpoint and started a debugging session (it's not necessary to start a debugging session explicitly when using this method). Using normal breakpoints in a snippet doesn't seem to work.
Debugging the backend can be done the 'normal' way (or are you trying to debug code you added to the backend yourself in any way?). I have absolutely no idea why you get 404 errors. Could you describe what you are doing to debug frontend / backend pages?
Cheers,
JanThis message has been ROT-13 encrypted twice for higher security. -
