Zikula Community

• thowden
  
  

  • Rank: Softmore
  • Registered: Nov 19, 2002
  • Last visit: Jan 22, 2010
  • Posts: 105

  Posted: Nov 28, 2006 - 05:25 PM

  Hi All
  
  I haven't looked at PN for some time and came back to it over the past few days with some new dev work I need to do.
  
  First up, GREAT WORK !! The MS2 release looks very good, the admin area looks like it has numerous improvements and as I wander through the backend the API looks good too.
  
  I rolled out a fresh install and made the following notes. I've put these here as I am not sure which are bugs and which rate as features. Mark, I guess you will redirect as appropriate.
  
  #1. The install.txt file docs/INSTALL.txt linked from the setup page does not exist.
  
  docs/install.html appears to be the correct link.
  
  #2. View Users - adjacent to the search box - the edit icon doesn't activate anything and the delete icon is labelled as edit.
  
  #3. The Admin screen displays the 'Postnuke Security Analyzer' block even when there are no issues (ie fixed the config.php chmod and removed the upgrade.php file)
  I would have expected this box to disappear. - I have since read that this is fixed.
  
  #4. Short URL enabled on the admin menu is not clear. The 'strip entry point from urls' has a note stating that '.htaccess required' which implies that the previous option of enabling Directory or File short urls - which is silent on .htaccess - do not require .htaccess - when if fact they do? Perhaps the entire section needs the note re .htaccess placed at the top, or to have the process install the basic .htaccess file to the PN root as a default once shorturls are enabled.
  
  #5. Main menu - Header_footer, errors, & blocks should not appear as items as they are not directly accessible, but I cannot see how these are appearing in the menu list as they are not in the Main Menu block. I'll keep searching but can I have a pointer please?
  
  #6. I have setup two copies of the .8MS2 One as live and the other as working. (neither are public, but I have my own SVN running and it will help my process). Funny thing is that I am using the same database and as such all the settings should be the same. The live copy works fine with shorturls (File) option set, but the working copy gives 404 errors on the shorturls. Turn off shorturls and both sites work fine. Is this a bug or am I missing something ?
  
  
  
  
  
  edited by: thowden, Nov 29, 2006 - 03:25 PM
  
  --
  cheers
  Tony
  
  Marble Bay : PostNuke Dev Work
  Wren/Maxwell : PostNuke Hosting
  
  

  • 
  •  
• markwest
  
  

  • Rank: Team Member
  • Registered: Mar 18, 2002
  • Last visit: Oct 21, 2009
  • Posts: 6606

  Posted: Nov 28, 2006 - 08:43 PM

  Tony,
  
  Thanks for the feedback. Can I recommend that, if you've looked at the MS2 build then to look at the daily builds too since this will have numerous fixes and enhancements (although will be occasionally broken ). Onto the specific points
  
  1) I believe this has already been fixed
  
  2) The way this works is that if you type part of a valid username into the text field then there'll be a backend (Ajax) lookup that will provide you with a list of matching usernames. Selecting one and then clicking edit will bring up the edit screen on this user.
  
  3)Fixed already
  
  4)File based short urls do require a .htaccess too but directory based ones don't. The difference the strip entry point makes is between index.php?/News/News_Article and /News/News_Article. The directory based urls .htaccess puts index.php back in.
  
  I agree this could be explained better....
  
  5) This can't be easily solved but is a problem that won't be an issue for most users. The default menu block is set to show all modules. This check simply looks for any user capable modules (a flag in the modules table). The blocks, errors and header_footer modules do actually offer some user functionality, although not that the end user can interact with, hence their listed.
  
  I wouldn't expect this default menu setup to remain very long after installation anyway....
  
  6) Not sure - there's not really enough info to go on...
  
  -Mark
  
  --
  Visit My homepage and Zikula themes.

  • 
  •  
• markwest
  
  

  • Rank: Team Member
  • Registered: Mar 18, 2002
  • Last visit: Oct 21, 2009
  • Posts: 6606

  Posted: Nov 28, 2006 - 11:23 PM

  For 4 i've made some improvements in the layout and text for this feature. Changes will be present in the next daily.
  
  -Mark
  
  --
  Visit My homepage and Zikula themes.

  • 
  •  
• thowden
  
  

  • Rank: Softmore
  • Registered: Nov 19, 2002
  • Last visit: Jan 22, 2010
  • Posts: 105

  Posted: Nov 29, 2006 - 08:51 AM

  Hi Mark
  
  Thanks for the info. I might come back to #5 after todays research.
  
  I had tried the daily for the 28th with these results:
  1. Copy over existing MS2 and replace default config.php with MS2 config.php - errors on undefined indexes
  2. Copy over existing MS2 and use install script to point to existing database (do not create) - errors on duplicated items
  3. Copy over existing MS2 and use install script with new / create DB - Notice: Undefined index: pn_hash_method in /opt/htdocs/thowden/postnuke8/includes/pnUser.php on line 106 & more
  4. Create entirely fresh install, new DB - Notice: Undefined index: pn_hash_method in /opt/htdocs/thowden/postnuke8/includes/pnUser.php on line 106 & more
  
  Noted: an install against an existing database will add some duplicated entries but fail on others. Perhaps allowing for the inadvertent selection of an existing database the script should stop or give some notice of intention?
  
  So I am guessing that I'll wait for another day
  
  I'll address #6 in another post as I think it's a separate thread.
  
  
  
  --
  cheers
  Tony
  
  Marble Bay : PostNuke Dev Work
  Wren/Maxwell : PostNuke Hosting
  
  

  • 
  •  
• Simon
  
  

  • Rank: Legend
  • Registered: Dec 11, 2002
  • Last visit: Oct 21, 2009
  • Posts: 11674

  Posted: Nov 29, 2006 - 11:34 PM

  There were some problems with DBUtil present in SVN for some time, the daily you used possibly contained those errors. Try the next one, they should be fixed.
  
  --
  itbegins.co.uk - Zikula Consulting
  
  birtwistle.me.uk - Personal Blog
  
  
  Please read the Support Guide

  • 
  •  
• thowden
  
  

  • Rank: Softmore
  • Registered: Nov 19, 2002
  • Last visit: Jan 22, 2010
  • Posts: 105

  Posted: Dec 04, 2006 - 01:34 PM

  Hi Simon
  
  Thanks. I have grabbed the 30th November daily and done a DB drop and created new. Its working fine.
  
  
  
  --
  cheers
  Tony
  
  Marble Bay : PostNuke Dev Work
  Wren/Maxwell : PostNuke Hosting
  
  

  • 
  •  
• thowden
  
  

  • Rank: Softmore
  • Registered: Nov 19, 2002
  • Last visit: Jan 22, 2010
  • Posts: 105

  Posted: Dec 04, 2006 - 02:09 PM

  Hi Mark
  
  

  Quote

  For 4 i've made some improvements in the layout and text for this feature. Changes will be present in the next daily.

  
  
  Just coming back to this and your changes in the most recent daily. Excellent ! The layout and control makes it much clearer for the reader/admin. Thanks.
  
  On my point 5.
  

  Quote

  This can't be easily solved but is a problem that won't be an issue for most users. The default menu block is set to show all modules. This check simply looks for any user capable modules (a flag in the modules table). The blocks, errors and header_footer modules do actually offer some user functionality, although not that the end user can interact with, hence their listed.
  

  
  
  If the module has user functions but not for user interaction then I would have thought it would be better to set the flag to 'no user function' or set another flag to indicate 'no user interface' or whatever the appropriate distinction is. I'll assume that the flag is currently determined on the existence of a user API file in the module directory?
  
  From your comment:
  

  Quote

  
  I wouldn't expect this default menu setup to remain very long after installation anyway....
  

  
  
  I gather that you don't see it as being used much, whereas I would have thought it would be used by default for many sites. It seems like a really neat feature for simplifying the menu management. Adding a new user style module would not require specifically adding a menu entry as well.
  
  Of course this is provided that the semi-user enabled modules and disabled modules are not listed. (i.e. Blocks & Theme Switching which is also listed but goes to a page that says its disabled)
  
  I'm not asking you to code it, but before I waste any time looking at it, is there a show-stopper that would prevent it happening?
  
  
  
  --
  cheers
  Tony
  
  Marble Bay : PostNuke Dev Work
  Wren/Maxwell : PostNuke Hosting
  
  

  • 
  •  
•  
•  

Users on-line

• mazdev

This list is based on users active over the last 60 minutes.