095 Home Stretch

3,975 Posts

Zaigham (aka zi) Reply #81, 19 years, 11 months ago

the new MODx Light theme works PERFECT for me

... its faster, the working progress indicators and a tree hide icons are placed right IMO.

MODx Green seems to have a problem, I m on FF 2.0 RC1 and IE 6.0, Tree Icons are messed up, context menu is not working in both browsers.

Same for MODx theme.

I am attaching the screenshots.

Zaigham R - MODX Professional | Skype | Email | Twitter

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

2,204 Posts

Dimmy Reply #82, 19 years, 11 months ago

Quote from: zi at Oct 06, 2006, 02:55 AM

the new MODx Light theme works PERFECT for me ... its faster, the working progress indicators and a tree hide icons are placed right IMO.

MODx Green seems to have a problem, I m on FF 2.0 RC1 and IE 6.0, Tree Icons are messed up, context menu is not working in both browsers.

Same for MODx theme.

I am attaching the screenshots.

I was just making screenshots to show the same thinks I noticed that some break character or mabe something else was present in the top left corner I hilighted the space to show also the icons are packt togetter with no H-spacing at all.

follow me on twitter: @dimmy01

3,975 Posts

Zaigham (aka zi) Reply #83, 19 years, 11 months ago

Captcha should change its residence? tongue

Zaigham R - MODX Professional | Skype | Email | Twitter

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

7,075 Posts

davidm Reply #84, 19 years, 11 months ago

Quote from: rthrash at Oct 06, 2006, 12:34 AM

If anyone would like to try the latest trunk, here’s a test build for you (rev 1624). This does not have the content changes in there but should be functionally complete.

David and Susan, I’d be particularly interested to see if this gets rid of your stuck/blank frames at top since they’ve all been merged (and peek at the tree context menu in safari too... heck of an improvement!).

Getting down to uploading and testing this out right now...

I’ll make sure to check the context menu in Safari

.: COO - Commerce Guys - Community Driven Innovation :.

MODx est l'outil id

1,611 Posts

ZAP Reply #85, 19 years, 11 months ago

Quote from: zi at Oct 06, 2006, 03:02 AM

Captcha should change its residence?

I use it on every installation, but is CAPTCHA legacy code considering that after three botched logins a user is blocked? Or is this to prevent people from fishing for usernames as well? I don’t think it necessarily needs removing even if it is superfluous, but and I correct that it essentially is?

"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

1,097 Posts

PaulGregory Reply #86, 19 years, 11 months ago

I never switch Captcha on for the Manager. I have no idea how many users out there do use this feature. I’m not mad happy on the default "3 false logins blocks the user for an hour" thing, it strikes me that people could go to /manager on lots of sites and deliberately screw up the predictable "admin" account at crucial moments.

However, I do like that admins have the choice. I’d rather that they could switch off the blocking, but admins can always change the logins to 60 and the time to 10 minutes or so if they want to rely on Captcha instead.

So: don’t remove it, but yes it needs to be in a better place than in that picture.

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!

2,204 Posts

Dimmy Reply #87, 19 years, 11 months ago

I think that Zi means that the position is not ok its positioned at the top but schould be next to the securitycode input field (below the logo at the bottom i think)

follow me on twitter: @dimmy01

7,075 Posts

davidm Reply #88, 19 years, 11 months ago

@Ryan: I did the upgrade to rev 1624 as instructed.

I don’t seem to have the blank bar issue anymore

I used FireBug while browsing the manager and there are a couple of errors there, don’t know if that’s important, bug I had identified those while trying to understand the blank submenu bar thing so here they are :

I get the following alerts from FireBug when I click on New Document :

parent.menu has no properties
index.php?a=4 (line 98)

When I do click on New Folder :

parent.menu has no properties
index.php?a=85 (line 98)

Idem for New Weblink

parent.menu has no properties
index.php?a=72 (line 98)

In Modules > Doc Manager

MODX_MEDIA_PATH is not defined modx.js (line 7)
parent.menu has no properties index.php?a=112&i... (line 159)
parent.menu has no properties functions.js (line 209)

In Tools > Export

parent.menu has no properties index.php?a=95 (line 91)

Now about the QuickEdit issue, am I still the only one with it ?

Here is the rendering problem I have :

It seems not to be a style problem, when I look at the page’s code :

<!-- Start QuickEdit toolbar -->
<div id="QE_Toolbar">
 <h1></h1>
 <ul>
 <li>

  <ul>
   <li><a href="javascript: qe.open('97');" title=" ">Contenu de la colonne de gauche</a></li><li><a href="javascript: qe.open('content');" title=" "></a></li><li><a href="javascript: qe.open('description');" title=" "></a></li><li><a href="javascript: qe.open('introtext');" title=" "></a></li><li><a href="javascript: qe.open('longtitle');" title=" "></a></li><li><a href="javascript: qe.open('pagetitle');" title=" "></a></li>
  </ul>
 </li> <li>
  <ul>
   <li><a id="QE_ShowLinks" class="checked" href="javascript:qe.toggleLinks();"></a></li><li><a href="javascript: qe.open('alias');" title=" "></a></li><li><a class="unchecked" href="javascript: qe.ajaxSave('cacheable', 'cacheable', '==1');" title=" "></a></li><li><a class="checked" href="javascript: qe.ajaxSave('hidemenu', 'hidemenu', '');" title=" "></a></li><li><a href="javascript: qe.open('menuindex');" title=" "></a></li><li><a href="javascript: qe.open('menutitle');" title=" "></a></li><li><a class="checked" href="javascript: qe.ajaxSave('published', 'published', '');" title=" "></a></li><li><a class="checked" href="javascript: qe.ajaxSave('searchable', 'searchable', '');" title=" "></a></li>
  </ul>
 </li> <li>

  <ul>
   <li><a id="QE_Manager" href="/~gican/manager/"></a></li><li><a id="QE_Help" href="http://www.modxcms.com/quickedit.html"></a></li><li><a id="QE_Logout" href="index.php?id=1&QuickEdit_logout=logout"></a></li>
  </ul>
 </li>
 </ul>
</div>
<!-- End QuickEdit toolbar -->

Translation strings are missing, while francais.inc.php is right there in assets/modules/quick_edit/lang/

???

If I change language (I tried to change first frond-end language to english, but then remembered manager language over-rides the setting, so I switched the manager to english but same issue).

I checked on PC doesn’t work either.

I erased the quick_edit folder and re-uploaded the files just to be sure... no change.
Also checked the module and plugin, everything seems to be in place.

I logged in into modx.it and I have also an issue with quickedit (I know it’s a rev1417 install, but...)

It’s really very strange...
Could it be the module GUID or something ?

.: COO - Commerce Guys - Community Driven Innovation :.

MODx est l'outil id

MODX Staff
12,272 Posts

Ryan Thrash Reply #89, 19 years, 11 months ago

It’s definitely a language issue and should be readily easy to resolve. I believe all the QuickEdit code should use the local language files in assets/modules/quick_edit/

Is your french file there?

Perhaps Garry who just sorted this out with the DocManager can give us some insight as to what’s going on... (oh no, another one for Garry ... sorry!) tongue

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

MODX Staff
12,272 Posts

Ryan Thrash Reply #90, 19 years, 11 months ago

I think all bets are off on the Firefox issues as that seems to be a rendering bug with their code. Try it in 1.5.0.7 or IE (or Safari or Opera) and you should see the right presentation. Let me know if this isn’t the case.

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