Installation, Configuration, & Upgrades  :: 
750 issue after admin-setting change
 Top

  • Hi,
    I have been playing with 726 for a few days but decided to take a look at 750. Did a fresh install, created a new DB and all was well everything worked except the usual well documented memberlists and messaging problems. I created a few test topics and posted some news.

    All worked well until I entered the admin - setting section and changed a few of the HTML options...after that clicking the 'read more' link from a front page article didn't work, it looked like it was loading but it never appeared you can see what I mean here
    http://www.amarc2002.co.uk/pn/index.php

    any one else have this problem?
  • Interesting. What happens if you set all the HTML options to "Allowed with parameters". This isn't advisable, as it can cause issues with security, but it will help you troubleshoot.
  • You have to turn on "load legacy" within the site settings.

    --
    best regards from Kiel, sailing city

    Steffen Voss

    Member of the PostNuke Steering Committee
    Read The Zikulan's Blog
  • I am running PN7.5 RC3 - and have an identical problem, the main Sections page loads and you can administer the Sections but after th emain page loads when you clicck a link the page flickers but the new page does not load,

    I have set the Load Legacy in Site Settings, and changed the HTML settings but to no avail. Where to next, I have started to think about breaking the Sections Index page to see if I can get anything but I don't believe the code is getting there at all.

    I am new to PN and PHP but old to code of other flavours, I have only been playing with this for the last couple of weeks and as a newbie finding documentation about how the blocks and modules hang together has been a challenge. I think its a great tool.
  • OK I struggled but the resolution was simple (isn't it always), in the Sections module in the Index.php file towards the end insert a line

    $req = pnVarCleanFromInput('reg');

    just before

    switch($req) {


    I'm sure this is not a clean solution but it works.

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