Issue with Admin Module after 1.3 -> 1.4.1 upgrade

Having trouble installing serendipity?
PeteHelgren
Regular
Posts: 18
Joined: Tue Mar 25, 2008 12:12 am

Re: Issue with Admin Module after 1.3 -> 1.4.1 upgrade

Post by PeteHelgren »

Thanks.

I little more looking around and I think I know what the issue was. I was looking at the FF cookie settings for a domain name of the domain with the blog. What I WASN'T doing was looking at the FF "Exception" list. It was THERE that I found that the domain was listed as "disabled". As soon as I deleted that, things got better.

But here is the final issue (I hope):

When the serendipityHTTPPath is set to /petesworkshop/blog/ whenever I click a link in the admin page it takes me to the login page again. But, if I change the serendipityHTTPPath to /blog/ the admin page functions work fine. However with THAT setting, I cannot navigate in the blog. When I click on the "next page" link, or any of the the archive links nothing happens.

If I change the serendipityHTTPPath back to /petesworkshop/blog/ then I can navigate using the "next page" and the "previous page" links except the archive links are broken.

baseURL is http://www.petesworkshop.com/blog/
serendipityPath is /www/zendcore/htdocs/petesworkshop/blog/

Not sure where the issue resides. Is it Apache or Serendipity? I am awfully close to getting it all working again. Something funky with these paths.

You can take a look. If you go to http://www.petesworkshop.com/blog/ you should be able to navigate forward and back, but if you click on an archive month, you will see that the path it renders is incorrect. Not sure why.
garvinhicking
Core Developer
Posts: 30022
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany
Contact:

Re: Issue with Admin Module after 1.3 -> 1.4.1 upgrade

Post by garvinhicking »

Hi!

Hm, what is strange is that you get serendipity on both /petesworkshop/ AND /blog/. Usually you can only get to the index.php through ONE of these URLs. I believe this is where a proxy might be interfering?!

So actually if your documentroot is .../petesworkshop/ then the only valid HTTPPath would be /blog/, and that is how it should be configured. you might need to purge all cookies belonging to a /petersworkshop/... HTTP path domain?

Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
PeteHelgren
Regular
Posts: 18
Joined: Tue Mar 25, 2008 12:12 am

Re: Issue with Admin Module after 1.3 -> 1.4.1 upgrade

Post by PeteHelgren »

Thanks again Garvin and thanks for being patient.

At this point I really have no explanation but I have a hack in mind that might fix the issue. Right now the calendar in the upper right seems to have the correct URL and the Archive entries do not. Looking through the code (and PHP is not my strong suit) I found what I think are the correct php files. The link in the calendar has this code behind it:
href="<?= $GLOBALS['tpl']['plugin_calendar_head']['uri_month'] ?>"><?= serendipity_formatTime("%B '%y", $GLOBALS['tpl']['plugin_calendar_head']['month_date']); ?>

..which in my case renders as:http://www.petesworkshop.com/blog/index ... 09/02.html for February

The Archive entries, which are incorrect (in my case) have the following code:
<a href="{$month.link_summary}">{/if}{$CONST.VIEW_TOPICS}{if $month.entry_count}</a>

..which renders as: http://www.petesworkshop.com/petesworks ... 09/02.html

Looks like the Calendar is a plugin in this case but can you suggest a change in the archive file that would render the URL like the Calendar plugin does? There may be a problem with the Apache server but it looks like if I can render the path like the Calendar plugin does, it will work for me.

Thanks.
garvinhicking
Core Developer
Posts: 30022
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany
Contact:

Re: Issue with Admin Module after 1.3 -> 1.4.1 upgrade

Post by garvinhicking »

Hi!

Hm, you are looking at the compiled PHP templates; usually you should only check the *.tpl files out in the /templates directory.

The variables come from the include/plugin_internal.inc.php file and they use the .uri_month variable from the serendipity_archiveDateUrl() function. The link_summary also comes freom the serendipity_archiveDateURL() function, so I don't see how they could be different.

The serendipity_archiveDateURL() function is declared in include/functions_permalinks.inc.php and only calls serendipity_rewruteURL() with a hard-coded "PATH_ARCHIVES" php constant. This constant is defined through the contents of what you entered as "Archives" link in the s9y configuration.

I also don't think that fixing this singular URL will help you; there must be more underlying trouble, all stemming IMHO from this /blog vs. /petesworkshop URL matter.

Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
PeteHelgren
Regular
Posts: 18
Joined: Tue Mar 25, 2008 12:12 am

Re: Issue with Admin Module after 1.3 -> 1.4.1 upgrade

Post by PeteHelgren »

"I also don't think that fixing this singular URL will help you; there must be more underlying trouble, all stemming IMHO from this /blog vs. /petesworkshop URL matter."

I agree, I just haven't been able to identify what I need to change in Apache in order to correct it.

What I find interesting is that *some* of the URL's referenced in the blog are correct and some are not. I understand that the PHP code is probably different in rendering the references, but it IS curious that the references are so different. In addition to the calendar entries being OK, I also noticed that author link and in the list of archives the "Older" link was correct.

Based on that, it looks like removing the 'serendipityHTTPPath' reference from the serendipity_rewriteURL seemed to fix the problems where they occurred. I changed plugin_internal.inc.php by removing the 'serendipityHTTPPath' reference from the serendipity_rewriteURL at about line 534 and again at about line 581. Yes, I know that it would be better to get to the bottom of the Apache config issue but this takes care of two of the more annoying problems at the moment. If I get the chance I may walk through more of the code to see if I can understand what is going on but at this point, it will do.

Thanks
Post Reply