Topic: 0.9.5 Public Beta 3 support  (Read 49384 times)

Pages: [1] 2 3 ... 11   Go Down

#1: 26-Sep-2006, 07:45 PM

JeremyL
Posts: 100

WWW
I just upgraded. Now I can no longer use my subdomain.

modxcms.domain.com redirects to domain.com/modxcms

It happens on the front end and the manager and also the urls in the site are being written that way.
« Last Edit: 27-Sep-2006, 01:03 AM by rthrash »

#2: 26-Sep-2006, 07:54 PM

Testers

ZAP
Posts: 1,619

This may have to do with a minor change to the .htaccess file. It now uses a RewriteBase directive before the RewriteRule lines. If you can't get it to work right with your subdomain, try going back to the previous .htaccess file and see if that fixes it.
"Things are not what they appear to be; nor are they otherwise." - Buddha

"Well, gee, Buddha - that wasn't very helpful..." - ZAP

Useful MODx links: documentation | wiki  | forum guidelines  | bugs & requests  | info you should include with your post | commercial support options

#3: 26-Sep-2006, 08:26 PM

JeremyL
Posts: 100

WWW
OK I now can use modx.domain.com but the urls being written in the content say www.domain.com/modxcms

Sounds like on install the www.domain.com/modxcms got written as the url to use. Is this store in the DB somewhere?

#4: 26-Sep-2006, 08:35 PM

Foundation

OpenGeek
MODx Co-Founder
Posts: 6,934

damn accurate caricatures...

WWW
OK I now can use modx.domain.com but the urls being written in the content say www.domain.com/modxcms

Sounds like on install the www.domain.com/modxcms got written as the url to use. Is this store in the DB somewhere?
It's determined by the server configuration.  Whatever PHP is reporting under $_SERVER['HTTP_HOST'] is gonna determine your domain.  Sounds like a misconfiguration of the web server in relation to PHP when setting up subdomains.

If you want to change it, set the base_path, base_url and site_url before the auto-configuration code in config.inc.php
Jason Coward
MODx Co-Founder
xPDO Founder
CTO @ Collabpad
work productively.
work intelligently.
work together.
Light is just a vibration of a note too. Everything is. You've got to keep that in mind.
  Frank Zappa

#5: 26-Sep-2006, 08:42 PM

JeremyL
Posts: 100

WWW
Nothing was wrong with $_SERVER['HTTP_HOST']. Not sure what was going on, but I did a change of front end template site wide and it fixed the issue. I had deleted the cache but maybe that didn't take. not sure what the issue was but it seems fixed now.

Must have been stored somewhere for a short time in cache when the htaccess was causing the other issue.
« Last Edit: 26-Sep-2006, 09:11 PM by JeremyL »

#6: 26-Sep-2006, 08:52 PM

JeremyL
Posts: 100

WWW
On Page /manager/index.php?a=76 (Manage resources page) there is a link not being parsed. This is in the source "/manager/media/style/.$theme./images/_tx_.gif"

I'm actually seeing a number of broken images, but the others I can't find errors in source. See the image I attached. The class="sectionHeader" seems to be the issue. I tried to re upload all styles in the manager and still no go.

Theres a great firefox plugin out there to help find the broken images that aren't obvious. http://chrispederick.com/work/webdeveloper/

it has a drop down to see all broken images on all pages in all the frame.


* imagemissing.JPG (131.95 KB, 1024x969 - viewed 487 times.)
« Last Edit: 26-Sep-2006, 09:31 PM by JeremyL »

#7: 26-Sep-2006, 09:09 PM

mjarecki
Posts: 35

Just a thought. I've noticed the line "RewriteBase /" has been added to the .htaccess file (or ht.access as the case may be).

Some people may sit there wondering why their site doesn't work anymore (as i did for a moment). I think that when you upgrade, there should be some sort of reminder, maybe near where it reminds you to delete the /install/ folder, to let people know to change the line RewriteBase incase their installation is in a subfolder. I.e. RewriteBase /root

Just a thought...

mark

#8: 26-Sep-2006, 09:27 PM

Foundation

rthrash
Posts: 11,348

WWW
Thanks JeremyL... the only theme that's been remotely gone over is the MODx Light theme. All bets are off with the plain MODx theme.
MODx is a content managmeent framework that allows web professionals to turn over sites to end-users for daily maintenance without worrying. Please help us help you when asking for assistance and read the wiki. Searching the forums from the top level helps, too.
Ryan Thrash
MODx Co-Founder
Principal @ Collabpad
work productively.
work intelligently.
work together.

#9: 26-Sep-2006, 11:24 PM

Testers

ZAP
Posts: 1,619

OK so there is a minor issue with the document tree PNG rollovers in the latest release that has an easy fix which will be committed soon. This issue will only be apparent when using IE6, since it is incapable of handling PNG transparency natively. The script uses a transparent gif and a filter workaround for IE6, but a couple things need to be changed to make it work properly.

First, the script is not finding the transparent gif. As a temporary fix, just upload a 1x1 transparent gif to the root of your manager directory and name it x.gif. Later this will probably live in the manager style folder, but for now this hasn't been decided.

The other issue is that the script needs for the images to have declared sizes or they shrink to the size of our transparent gif (1x1). So this could be set in the image tags, the CSS file, or the JavaScript that does the replacing. For now we're doing it in the JavaScript.

Open the file assets/js/pngbehavior.htc and make lines 63-68 look like this:

Code:
// set filter
element.runtimeStyle.filter = "progid:DXImageTransform.Microsoft." +
"AlphaImageLoader(src='" + src + "',sizingMethod='scale')";
   element.style.width = element.width + "px";
    element.style.height = element.height + "px";
}

All you've done is add the two lines that set the correct size for the images after being replaced by the gif.

And lastly, there's a tiny tweak to the CSS file to make the document tree's icon bar not get taller on rollover in IE6.

Open manager/media/style/MODxLight/style.css and change the coolButtonHover class at line 913 to the following:

.coolButtonHover {
    border: 1px solid #006400;
    padding: 2px 4px 1px 4px;
    height: 20px !important;
    height: 17px;
    background: #dee9c6;
}

That fixed everything for me. I gather that future versions of this release will have this corrected, and the fix may be slightly different. So make sure you look ahead in this thread and see if that's the case before you bother doing this...
"Things are not what they appear to be; nor are they otherwise." - Buddha

"Well, gee, Buddha - that wasn't very helpful..." - ZAP

Useful MODx links: documentation | wiki  | forum guidelines  | bugs & requests  | info you should include with your post | commercial support options

#10: 26-Sep-2006, 11:30 PM

mjarecki
Posts: 35

Whenever I edit a template, the text "<? echo isset($content['newcategory']) ? $con" is always found in the New Category text field.

I went through every template and this appears in every New Category text field. I accidentally saved the document with that in the field and it created a new category.

It is persistent and doesn't go away, even if i save to an existing category and delete the "<? echo isset($content['newcategory']) ? $con" from the text field.

I would also like to be able to delete categories (especially ones with nothing in them). I know I can do it through MySQL, but it would be nice to have a tab called categories, with a list of categories and the word delete next to it. The Combined View doesn't quite do this.

Cheers

mark

#11: 26-Sep-2006, 11:33 PM

mjarecki
Posts: 35

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

#12: 26-Sep-2006, 11:55 PM

mjarecki
Posts: 35

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?

#13: 27-Sep-2006, 01:04 AM

Foundation

rthrash
Posts: 11,348

WWW
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.
MODx is a content managmeent framework that allows web professionals to turn over sites to end-users for daily maintenance without worrying. Please help us help you when asking for assistance and read the wiki. Searching the forums from the top level helps, too.
Ryan Thrash
MODx Co-Founder
Principal @ Collabpad
work productively.
work intelligently.
work together.

#14: 27-Sep-2006, 03:25 AM

Testers

The Man Can!
Posts: 345

WWW
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?
« Last Edit: 27-Sep-2006, 03:50 AM by The Man Can! »
Need MODx Ecommerce? Try FoxyCart!

#15: 27-Sep-2006, 04:38 AM

mjarecki
Posts: 35

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
« Last Edit: 27-Sep-2006, 04:41 AM by mjarecki »

#16: 27-Sep-2006, 05:41 AM

Coding Team

garryn
Posts: 1,390

WWW
Quote from: mjarecki
- 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.

#17: 27-Sep-2006, 07:16 AM

Coding Team

garryn
Posts: 1,390

WWW
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.

« Last Edit: 27-Sep-2006, 10:55 AM by garryn »

#18: 27-Sep-2006, 09:36 AM

jaroslav
Posts: 31

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
Code:
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.

#19: 27-Sep-2006, 10:12 AM

Foundation

OpenGeek
MODx Co-Founder
Posts: 6,934

damn accurate caricatures...

WWW
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.

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
Code:
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?

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
MODx Co-Founder
xPDO Founder
CTO @ Collabpad
work productively.
work intelligently.
work together.
Light is just a vibration of a note too. Everything is. You've got to keep that in mind.
  Frank Zappa

#20: 27-Sep-2006, 10:25 AM

PaulGregory
MODx's midnight runner
Posts: 1,097

MODx's midnight runner

WWW
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.

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?
« Last Edit: 27-Sep-2006, 10:30 AM by PaulGregory »
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!
Pages: [1] 2 3 ... 11   Go Up
0 Members and 1 Guest are viewing this topic.