0.9.5 Public Beta 5 (rev 1785)

MODX Staff
12,272 Posts

Ryan Thrash Reply #1, 20 years ago

This should be very near the end, finally! (We even debated making this an RC.) As such, we’d like to get 095 out as quickly as possible, and need your help to make it the best release to date. If you notice a problem in your native language, please try the default English language file to see if it exists there as well. If not, please file a bug report requesting translation updates per the instructions below.

If you have requests to change functionality or you are confident you’ve found a bug in this beta (or a remaining issue exists from the previous betas), please add an appropriate bug report/feature request to our bug tracker. Make sure to flag the identified version as beta 5. Even better, if you have code that fixes the problem, please include your suggested code changes there; this goes for CSS updates to any of the templates as well.

Feel free to link to forum discussions about specific issues, but we need to see every proposed change to MODx code be accompanied by a Flyspray bug number. Otherwise, it’s likely many of these good catches and great additions to the code will be overlooked at some point, either in this release, or in other branches that are being developed in parallel.

Please try and keep this forum limited to questions or quick informative statements like "Here’s a bug I found in 1785, ...[some details]..., see FS#967 for a suggested fix", and save more detailed error information and suggested code changes for the bug report itself. This will help us tackle some of these issues much more quickly.

In other words, if we don’t see a bug report or feature request in the bugtracker, you’re not allowed to cry if the fix or feature doesn’t make it into a release. wink

Thanks for your feedback to date and looking forward to rapidly bringing this to a release state.

LATE ADDED ADMIN NOTE: Just as an FYI, I’ll ~~probably~~ am deleting and crossing out posts as things are resolved to try to keep this thread more organized and speed the release date as much as possible. Thanks for all the reports ... it’s tremendously helpful. For reference, there is no policy on setting priorities on bugs, just use your best judgment and we’ll adjust as needed.

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

835 Posts

aour Reply #2, 20 years ago

Hi

It’s installed without exemple data and minimal template use dropmenu but dropmenu is no more installed!

FS#588

Aour

[img]http://modxcms.com/assets/images/promo/modx-most-promising-open-source-winner.gif[/img]
[font=Verdana]Recherche | Support Francophone |Demander de l'aide | Documentation FR | Rapporter un Bug | [url=http://modxcms.com/forums/index.php/topic,2533.0.html][b]R

283 Posts

OncleBen31 Reply #3, 20 years ago

Quote from: Vait at Oct 24, 2006, 03:54 AM

downloaded and upgraded from modx b3 to b5, now Iam facing a problem... cant publish the content. Cant tick to publich content. Also if I set all the documents to be published, they still dont get published. SOS
Quote from: garryn at Oct 24, 2006, 04:09 AM

Hi Vait, did you run the installer to complete the upgrade? There’s a change in the publishing permissions between beta3 and beta5 that will need the installer running for it to do the necessary updates.

I’ve a similar problem with a SVN release. It disappeared by logout and login in the manager.

Admin note: solved the problem

Follow my contributions to open source on Oncleben31.cc

3,975 Posts

Zaigham (aka zi) Reply #4, 20 years ago

A note to all users who are upgrading, when you complete the upgrade, close your browser and re-open it, or at least log out before upgrading. This will save you from lots of headaches

.

Enjoy shiny new MODx!

zi

Zaigham R - MODX Professional | Skype | Email | Twitter

Digging the interwebs for #MODX gems and bringing it to you. modx.link

502 Posts

ajayre Reply #5, 20 years ago

Some problems with using TinyMCE and creating links. See: http://modxcms.com/bugs/task/589

62 Posts

checco Reply #6, 20 years ago

Quote from: ajayre at Oct 24, 2006, 02:01 PM

Problem with Quickedit and private pages: http://modxcms.com/bugs/task/590

Andy

Hi
thanks a lot for this great software and for all the work

On this new beta 5 I have a similar problem with TinyMCE. In the manager and also in the QuickEdit I can’t see any icon. I try with log out and in or closing the browser but nothing...
Any idea?
Ciao

MODX Staff
10,725 Posts

opengeek Reply #7, 20 years ago

Ok, we’ve identified the problem with installing TinyMCE I believe, and it would likely affect any plugin which you are upgrading that has configuration properties which have changed since your version. A solution is being worked on, but to get around this for the time being, you can remove or rename the existing plugins which you intend to upgrade during the installation, then run the install (again, if you already have). This way the plugins are treated as new and you’ll get the proper configuration properties installed.

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

254 Posts

kudolink Reply #8, 20 years ago

[s]I’ve filed a new bug at FS#596.
The bug is in the regClientCSS function, it lacks a " (double quote) after the css file url attribute, so the tag is wrong and it’s not parsed by some browser.

I’ve found the bug in subversions 1529 - 1533 - 1775 - 1785 so I think about all the release of the 0.95beta are potentially bugged.

This is the function from subversion 1785, so BUGGED (the error is in the line 2147).
Lines 2139-2149:

    # Registers Client-side CSS scripts - these scripts are loaded at inside the <head> tag
    function regClientCSS($src) {
        if (isset ($this->loadedjscripts[$src]) && $this->loadedjscripts[$src])
            return '';
        $this->loadedjscripts[$src]= true;
        if (strpos(strtolower($src), "<style") !== false || strpos(strtolower($src), "<link") !== false) {
            $this->sjscripts[count($this->sjscripts)]= $src;
        } else {
            $this->sjscripts[count($this->sjscripts)]= '<!-- MODx registered -->' . "\n" . '  <link rel="stylesheet" href="' . $src . ' />'; // <-typo!
        }
    }

~~And this is the corrected function, good for subversions 1529 - 1533 - 1775 - 1785:~~

    # Registers Client-side CSS scripts - these scripts are loaded at inside the <head> tag
    function regClientCSS($src) {
        if (isset ($this->loadedjscripts[$src]) && $this->loadedjscripts[$src])
            return '';
        $this->loadedjscripts[$src]= true;
        if (strpos(strtolower($src), "<style") !== false || strpos(strtolower($src), "<link") !== false) {
            $this->sjscripts[count($this->sjscripts)]= $src;
        } else {
            $this->sjscripts[count($this->sjscripts)]= '<!-- MODx registered -->' . "\n" . '  <link rel="stylesheet" href="' . $src . '" />'; // Corrected
        }
    }

~~Thank you.~~

kudo
www.kudolink.com - webdesign (surprised?)

[img]http://www.kudolink.com/kudolinkcom.png[/img] [sup]proudly uses[/sup] [img]http://www.kudolink.com/modx.png[/img]

1,010 Posts

TobyL Reply #9, 20 years ago

Quote from: rthrash at Oct 24, 2006, 10:23 AM

Quote from: TobyL at Oct 24, 2006, 10:15 AM

I also noticed that in the Manager Theme settings in the site configuration I’m getting an extra ’.svn’ theme (Wonder how that would look?) Yes, I know what’s causing that but do you reckon there’s any possibility the code could be changed to ignore dot files ? Unlike Nix systems, Windows unfortunately doesn’t respect dot files with the respect they deserve.

~~Please file a bug report on the preview window. It’s related to removing the hard-coded styles and needing a style added to the stylesheets.~~

~~Have filed bug report #597 for the preview window issue, and a feature request (#598) for the directory showing in the theme selection~~

eForm | eForm support | eForm @ wiki

133 Posts

piwaille Reply #10, 20 years ago

Quote from: Vait at Oct 24, 2006, 03:54 AM

downloaded and upgraded from modx b3 to b5, now Iam facing a problem... cant publish the content. Cant tick to publich content. Also if I set all the documents to be published, they still dont get published. SOS

Just wanted to approve the thing : there must be something with the "upgrade".
I upgraded beta3 -> beta5 and my builtin admin was no more able to publish/unpublish (*)
My redactors (which role has ability for publishing) where able to
I was able to make a new role with all rights (even publishing)

(*) I was not able to click in the contextual menu and the option was grayed in tab.

When I proceed upgrade, I did take care that nobody was sufing my test site nor the manager.

I did an second upgrade... things went right back...
but du to the number of people having the problem... there must be something (sorry not being able to give your more info)