That's it!

It's there in the default template set, but not in the clone I made.

After I upgraded I re-generated all the templates that were marked. I guess maybe I still don't understand the upgrad process fully.

Why arent these changes reflected in my cloned templates and what do I need to do to get them there?

Thank you *SO* much!!

jp

Greetings.

I apologise, this is not a true development question. It does involve the internals of XOOPS security however and I was not getting any responses posting in some of the other forums. I hope that by posting here, someone with knowledge of XOOPS internals might be able to help.

Can someone please explain to me what this is doing?



More specifically, what is the call to $GLOBALS['xoopsSecurity']->check() doing?

I just noticed that on one of my sites, I cannot register a request to be notified of events (like the Global "Notify me of blah blah blah" or sub-global-level like "Notify me when a new comment is posted for this item.").

When I hit "Update Now", it winds up re-directing me without saving the notification request.

I've traced it through this far:

When I hit "Update Now", the form executes notification_update.php from the XOOPS root.

I get as far as this section of notification_update.php:



where it takes the "true" path.

The call to $GLOBALS['xoopsSecurity']->getErrors() is returning an empty array (as near as I can tell).

I don't know enough about the internals of XOOPS to understand why this is failing. I have this working properly on another site. The biggest difference I can see between the two sites is the site that is working was a full install of XOOPS 2.0.13 whereas the site with broken notification is an upgrade to XOOPS 2.0.13.

Any help would be much appreciated. Thanks.

JP

Greetings.

I just noticed that on one of my sites, I cannot register a request to be notified of events (like the Global "Notify me of blah blah blah" or sub-global-level "Notify me when a new comment is posted for this item.").

When I hit "Update Now", it winds up re-directing me without saving the notification request.

I've traced it through this far:

When I hit "Update Now", the form executes notification_update.php from the XOOPS root.

I get as far as this section of notification_update.php:

if (!$GLOBALS['xoopsSecurity']->check()) {
redirect_header($_POST['not_redirect'], 3, implode('<br />', $GLOBALS['xoopsSecurity']->getErrors()));
exit();
}

where it takes the "true" path.

The call to $GLOBALS['xoopsSecurity']->getErrors() is returning an empty array.

I don't know enough about the internals of XOOPS to understand why this is failing. I have this working properly on another site. The biggest difference I can see between the two sites is the site that is working was a full install of XOOPS 2.0.13 whereas the site with broken notification is an upgrade to XOOPS 2.0.13.

Any help would be much appreciated. Thanks.

JP

Things are worse than I thought.

This is not a piCal issue (or at least it's not limited to piCal). Notification subcription is broken on the entire site.

Any help would be much appreciated.

JP

Greetings.

I just noticed that on one of my sites, I cannot register a request to be notified of events (like the Global "Notify me when a new event is created." or the Event-level "Notify me when a new comment is posted for this item.").

When I hit "Update Now", it winds up re-directing me to the main calendar page. Whemn I check, my request for notification is not there.

I've traced it through this far:

When I hit "Update Now", the form executes notification_update.php from the XOOPS root.

I get as far as this section of notification_update.php:

if (!$GLOBALS['xoopsSecurity']->check()) {
redirect_header($_POST['not_redirect'], 3, implode('<br />', $GLOBALS['xoopsSecurity']->getErrors()));
exit();
}

where it takes the "true" path.

The call to $GLOBALS['xoopsSecurity']->getErrors() is returning an empty array.

I don't know enough about the internals of XOOPS to understand why this is failing. I have this working properly on another site.

Any help would be much appreciated. Thanks.

JP

That did it!! Thank you *SO* much. It even fixed the problem with the piCal block!!

I did not know about having to update the system module after the copy-over (to be fair, zimmi88 mentioned it earlier in the thread, but I didn't understand what that meant), nor did I know about having to re-gen the templates.

Thanks for that great tutorial!!


Odd though, the preview of the HTML Block is still messed up, but it renders just fine in the block.

You are my hero or heroin!!

jp

OK, I had to give up and drop back to 2.0.9.2 and have left it there till now.

I'm ready to tackle this anew, so I've re-applied th 2.0.9.2 to 2.0.10 upgrade.

I'm back to where I left off - the custom HTML block on main page is not rendering, nor is the piCal mini-block.

The Custom Block has an HTML table and two javascript blocks - one at the begining and one at the end.

In it's original form I cannot even preview it. Instead of getting the pop-up window I get a partial rendering at the end of the admin page for this block that includes a bunch of ill-formed win.document.writeln(" statements ( they all cut off at the '("' ).

It looked to me initially like the commenting-out of the javascript ( <!-- --> ) in my block text was throwing this for a loop so I removed all the javascript.

When I do this, the good news is I am then able to preview it and it shows up fine in the pop-up. The bad news is when I save it, the block still will not render. I've stripped out almost all of the text between the td tags and it still won't render when I save it.

Has something changed with how the Custom Block (HTML) renders in 2.0.10?

I'm willing to write-off the piCal issue as my needing to upgrade my version of piCal, but the Custom Block (HTML) is core.

Any thoughts on what's wrong and what I can do about it?

As always, any help is much appreciated.

JP

<blow><blow>Is this thing on? I know you're out there, I can hear you all breathing ....

JP

I'm behind on my upgrades and decided to try to get caught up tonight.

I'm currently running XOOPS 2.0.9.2 and tried applying the 2.0.9.2 to 2.0.9.10 patch. I have a custom block on my main page and I also have a block for piCal 0.60 (I know, also woefully out of date <sigh>). Both of these blocks failed to render. The frames for them were there, but they were empty.

I turned on various levels of debugging; didn't see any errors.

I took a backup prior to applying the patch and have successfully backed out.

Can anybody point me in the right direction on where things have gone oblong?

Thanks,

JP

Geetings all.

I was wondering if there was a setting so that priviate forums are visible only to authorized users as opposed to the default behaviour which is that it is visible to all but if an unauthorized user attempts to access it they get a message indicating they are not authorized.

It would be better for my site if the forum list contained only forums for which the user was authorized.

Thanks for any advice.

JP