0.9.5 Public Beta 3 support

35 Posts

mjarecki Reply #11, 20 years ago

The same thing happens in the Chunks New Category text field. Though it doesn’t happen in any of the other New Category fields.

35 Posts

mjarecki Reply #12, 20 years ago

Another thing I’ve noticed is that I can’t create a new Template or Chunk.

i get a "Not Found. The requested URL /index.php was not found on this server." message.

This does not happen when trying to create a new TV, Snippet or Plug-in.

Any ideas?

MODX Staff
12,272 Posts

Ryan Thrash Reply #13, 20 years ago

Note, manager anomalies in IE should be fixed in rev 1531 on the beta download page. You should be able to upgrade simply by updating your manager folder. If you do this, remember to keep your config.inc.php file.

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

361 Posts

The Man Can! Reply #14, 20 years ago

New MODxLight theme is beautiful, but seems like on any and every Mac / OS X browser I’ve tried the default text size for textboxes is about 7px or 8px. Near impossible to read. Looks great on XP though.

EDIT: Did beta 3 break Ditto tag calls or is it just me? Was working fine (if a bit quirky) right before the upgrade from beta 2. Now the only tagMode that does anything at all is onlyAllTags, and it’s returning absolutely everything regardless of tags. Can anybody confirm this? I’m restoring back to beta 2 in the meantime, but am really curious if it’s just me or not.

EDIT AGAIN: Yeah, just restored files (didn’t restore the database) back to beta 2 and my ditto calls using tags started working again. It’s the stock install of Ditto 1.0.2, and I’ve checked the files that work (beta 2) against the beta 3 files and they look identical, so maybe it’s something else? Something Ditto relies on for tagging has been removed/changed?

Need MODx Ecommerce? Try FoxyCart!

35 Posts

mjarecki Reply #15, 20 years ago

I tried a clean install on my system, installing rev.1531 from scratch and the problems I mentioned earlier still persist.

I installed ModX with no sample site, chunks or deprecated snippets and have made NO modifications other than adding a simple document called hello, and marking yes to all friendly URL Setting to Yes. The issues I have include:

- i still can’t create new Templates or Chunks - I get the error message: Not Found. The requested URL /index.php was not found on this server."
- When i click on the default Minimal Template, the string "<? echo isset($content[’newcategory’]) ? $con" persistently fills the New Category text field.
- the "Working" icon often persists, blocking access to the logout link (this is in ModX Green & Light).
- The text in the Content text area of a document, when using ModX Light is tiny and illegible on a OS X system.

I’ve modified the .htaccess file to RewriteBase /trunk (the same as the directory in which ModX is installed)

I’m using Intel OS X 10.4.7, Camino, MySQL MySQL - 5.0.24-standard, PHP 5.1.6. I’m not sure what’s happened, as the other beta releases I’ve tried have been working pretty-well.

Any ideas?

mark

MODX Staff
1,535 Posts

Garry Nutting Reply #16, 20 years ago

- i still can’t create new Templates or Chunks - I get the error message: Not Found. The requested URL /index.php was not found on this server."
- When i click on the default Minimal Template, the string "<? echo isset($content[’newcategory’]) ? $con" persistently fills the New Category text field.

There’s a few known issues with the template and chunk screens for beta 3 - quite a few big changes have been made to the files between beta 2 and beta 3 with some obvious further adjustments that still need to be made.

Sorry folks, blame is firmly on me for that one embarrassed

I will get a fix commited to SVN as soon as I can.

Garry Nutting
Senior Developer
MODX, LLC

Email: [email protected]
Twitter: @garryn
Web: modx.com

MODX Staff
1,535 Posts

Garry Nutting Reply #17, 20 years ago

Okay, I have modified the files causing the problem with the templates and chunks, and committed the changes to my branch in SVN.

EDIT: Removed patch as it’s now included in the beta 3 package.

Garry Nutting
Senior Developer
MODX, LLC

Email: [email protected]
Twitter: @garryn
Web: modx.com

31 Posts

jaroslav Reply #18, 20 years ago

QuickEdit module seems not working in 0.9.5 Beta 3 (and in 0.9.5 Beta 2). I think it is a "core" module for forthcoming 0.9.5, so I was decided to post this report in Beta Support topic.

It seems in Beta’s QuickEdit module is totally rewritten, but not finished or not properly merged in repository. For now, it is impossible to use QuickEdit with or without "default site content" installation: it not works even on empty pages with, for example, [*#content*] tag. (WinXP without Service Packs, WinXP SP1, WinXP SP2, IE 6.0)

1) First bug: it is impossible to show popup window with (or without) RichEdit DHTML control when "Edit content" button is pressed.
I found one hack to correct this. In assets/modules/quick_edit/javascript/QuickEdit.js "name" parameter of "open" method of "QuickEdit" class is constructed as

var name = 'QuickEditor-'+this.pageID+'-'+contentID;

Change "minus" characters to "_" (underscore), and it will work. Some others characters also will not work.
Very strange bug, and I don’t think my dirty hack is the solution yet.

2) Second bug: dropdown menus of QuickEdit panel are not shown. If you click "content", "settings" or "go" buttons, nothing happens.
I discovered that moo.fx effect (top-down sliding) is called successfully, so menu "height" CSS value changes properly. But nothing on screen... I think it may be due to some CSS or behaviours conflict(s), or so.

I need Frontend-editing future very much, and I not have for now enough time to dig in javascript / CSS. If someone has working Frontend-editing solution for 0.9.5 Beta 3, I will be very appreciate.

P.S. I’m new in MODx, as of in English language, so please sorry for possible mistakes.

MODX Staff
10,725 Posts

opengeek Reply #19, 20 years ago

Quote from: jaroslav at Sep 27, 2006, 09:36 AM

QuickEdit module seems not working in 0.9.5 Beta 3 (and in 0.9.5 Beta 2). I think it is a "core" module for forthcoming 0.9.5, so I was decided to post this report in Beta Support topic.

It seems in Beta’s QuickEdit module is totally rewritten, but not finished or not properly merged in repository. For now, it is impossible to use QuickEdit with or without "default site content" installation: it not works even on empty pages with, for example, [*#content*] tag. (WinXP without Service Packs, WinXP SP1, WinXP SP2, IE 6.0)

Where do you see this? I do not believe it has been totally rewritten. In fact, it should be performing much better now as some QuickEdit code in previous versions was erroneously being executed regardless if your were logged in as a manager.

Quote from: jaroslav at Sep 27, 2006, 09:36 AM

1) First bug: it is impossible to show popup window with (or without) RichEdit DHTML control when "Edit content" button is pressed.
I found one hack to correct this. In assets/modules/quick_edit/javascript/QuickEdit.js "name" parameter of "open" method of "QuickEdit" class is constructed as
var name = 'QuickEditor-'+this.pageID+'-'+contentID;
Change "minus" characters to "_" (underscore), and it will work. Some others characters also will not work.
Very strange bug, and I don’t think my dirty hack is the solution yet.

I’m not getting this behavior at all; I’ve tried upgrades and new installations. Can anyone else reproduce?

Quote from: jaroslav at Sep 27, 2006, 09:36 AM

2) Second bug: dropdown menus of QuickEdit panel are not shown. If you click "content", "settings" or "go" buttons, nothing happens.
I discovered that moo.fx effect (top-down sliding) is called successfully, so menu "height" CSS value changes properly. But nothing on screen... I think it may be due to some CSS or behaviours conflict(s), or so.

Again, I certainly can’t reproduce this is in the default content. Anyone else?

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

1,097 Posts

PaulGregory Reply #20, 20 years ago

Firstly, Jaroslav’s error report applies to Beta 2 also, and lots of people have tried that so I’d be surprised if this was widespread.
I’m also confused as to why 3 different XP installs (no SP, SP1, SP2) but the "same" browser all have the error. This suggests that something is missing/wrong in the specific install/website.

I have had QuickEdit go "mad" and not show any text, but I thought that was probably a memory issue on my PC.
EDIT: By this I mean the menu text has disappeared. I’ve not had any problems calling up the input box, but then again I do use Firefox.

Quote from: OpenGeek at Sep 27, 2006, 10:12 AM

I do not believe it has been totally rewritten.

Well, someone’s switched it to using moo.fx.. 0.9.2.1 used script.aculo.us. I suspect that’s where the issue lies. Jaroslav, do you have script.aculo.us as well on your site?

EDIT2: Jaroslav, is your Beta 3 from the SVN or from the zip?

EDIT3: Jaroslav, what do you mean by RichEdit DHTML control? The one that comes with MODx or one you’ve added in yourself?

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!