Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#496 2009-10-15 16:46:39
- si.b
- New Member
- Registered: 2009-10-14
- Posts: 5
Re: gbp_permanent_links
Of course – I considered upgrading txp, but didn’t want to risk buggering something up without knowing it would actually make a difference!:
Textpattern version: 4.0.4 (r1956)
Last Update: 2007-05-18 15:13:40/2007-05-18 15:10:26
Document root: e:\domains\j\juliaarmstrong.com\user\htdocs (E:\domains\j\juliaarmstrong.com\user\htdocs)
$path_to_site: E:\domains\j\juliaarmstrong.com\user\htdocs
Textpattern path: E:\domains\j\juliaarmstrong.com\user\htdocs\textpattern
Permanent link mode: messy
upload_tmp_dir: C:\WINDOWS\Temp
Temporary directory path: e:\domains\j\juliaarmstrong.com\user\htdocs\textpattern\tmp
Site URL: www.juliaarmstrong.com
PHP version: 5.2.6
Server Local Time: 2009-10-15 17:44:37
MySQL: 5.0.77
Locale: English_United Kingdom.1252
Server: Microsoft-IIS/6.0
PHP Server API: cgi-fcgi
RFC 2616 headers: 0
Server OS: Windows NT 5.2
Active plugins: zem_contact_reborn-4.0.3.16, zem_contact_lang-4.0.3.02, dca_pop-0.1, wet_quicklink-0.5, wet_peex-0.4, SimplePie Plugin-1.2.2, rah_metas-1.1, jmd_sitemap-0.1.2
Pre-flight check:
————————————
E:\domains\j\juliaarmstrong.com\user\htdocs\textpattern\setup\ still exists
Missing files: E:\domains\j\juliaarmstrong.com\user\htdocs\textpattern/publish/atom.php
Some Textpattern files have been modified: /include/txp_category.php,
/include/txp_plugin.php,
/include/txp_auth.php,
/include/txp_form.php,
/include/txp_section.php,
/include/txp_tag.php,
/include/txp_list.php,
/include/txp_page.php,
/include/txp_discuss.php,
/include/txp_prefs.php,
/include/txp_log.php,
/include/txp_preview.php,
/include/txp_image.php,
/include/txp_article.php,
/include/txp_css.php,
/include/txp_admin.php,
/include/txp_link.php,
/include/txp_diag.php,
/include/txp_file.php,
/include/txp_import.php,
/lib/admin_config.php,
/lib/txplib_misc.php,
/lib/taglib.php,
/lib/txplib_head.php,
/lib/classTextile.php,
/lib/txplib_html.php,
/lib/txplib_db.php,
/lib/IXRClass.php,
/lib/txplib_forms.php,
/lib/class.thumb.php,
/lib/constants.php,
/lib/txplib_update.php,
/lib/txplib_wrapper.php,
/publish/taghandlers.php,
/publish/log.php,
/publish/comment.php,
/publish/search.php,
/publish/rss.php,
/publish.php,
/index.php,
/css.php
The following PHP functions (which may be necessary to run Textpattern) are disabled on your server: shell_exec,exec,system,passthru, popen,proc_open,pass_thru,pcntl_exec,proc_close,proc_get_status,proc_nice,proc_terminate,dl,pclose,pfsockopen,posix_kill,posix_mkfifo
————————————
.htaccess file contents:
————————————
#DirectoryIndex index.php index.html
#Options +FollowSymLinks
#RewriteBase /relative/web/path/
<IfModule mod_rewrite.c> RewriteEngine On RewriteCond %{REQUEST_FILENAME} -f [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^(.+) – [PT,L]
RewriteRule ^(.*) index.php </IfModule>#php_value register_globals 0
————————————
Offline
#497 2009-10-15 18:10:02
Re: gbp_permanent_links
Uhm… There should be a clean url test message in the page, above textarea, if I remember right. Anyway, your txp install is heavily modified! Are you aware of this? Plus, a lot of function are disabled on your server, even if I don’t know if they are related to clean urls.
You should try a fresh install of 4.0.4, if you don’t want to upgrade (but why not?). At the moment, it could be anything: try an unmodified install and then you can see what’s wrong.
Offline
#498 2009-10-15 23:43:45
Re: gbp_permanent_links
Zanza wrote:
Uhm… your txp install is heavily modified! Are you aware of this? …. try an unmodified install and then you can see what’s wrong.
In Txp 4.0.4 those unmodified files could have been uploaded incorrectly. Wrong line endings etc… I’ve seen that many times probably nothing to worry about.
Plus, a lot of function are disabled on your server, even if I don’t know if they are related to clean urls.
Those functions aren’t required by gbp_permanent_links and shouldn’t be required TXP (95% sure).
Maybe you could test a fresh install of TXP 4.2.0 to see if this is a problem with 4.0.4. Or upgrade it shouldn’t be too painful if at all. Be sure to back everything up first tho!
Offline
#499 2009-10-17 08:08:41
- si.b
- New Member
- Registered: 2009-10-14
- Posts: 5
Re: gbp_permanent_links
Thanks for the comments guys – will try an upgrade and keep you posted.
Offline
#500 2009-10-18 20:43:29
Re: gbp_permanent_links
For some reason when gbp_permanent_links is enabled bad URLs are being generated for txp:link_to_next and txp:link_to_prev the generated URLs look something like the following…
http://website/blog/—permlink_format_error—/203/
Offline
#501 2009-10-18 21:00:35
Re: gbp_permanent_links
I think I know what the problem was… the error in the URL was because I was in debug mode of gbp_permanent_links. And I believe the reason there was an error is I had “automatically_append_title” turned on, but I didn’t have a rule that used the title. At least I think so.
Things are working fine now.
mericson wrote:
For some reason when gbp_permanent_links is enabled bad URLs are being generated for txp:link_to_next and txp:link_to_prev the generated URLs look something like the following…
http://website/blog/—permlink_format_error—/203/
Offline
#502 2009-10-18 21:07:32
Re: gbp_permanent_links
mericson wrote:
For some reason when gbp_permanent_links is enabled bad URLs are being generated for txp:link_to_next and txp:link_to_prev the generated URLs look something like the following…
That’ll change if you’re in live mode.
Offline
#503 2009-10-26 20:37:34
Re: gbp_permanent_links
Hi graeme,
you early mentioned that gbp_permanent_links should be compatible with MLP.
I’ve set up a TXP install wih MLP + gbp_p_l, but haven’t try any crazy thing yet.
So far, I’ve noticed that when gbp_p_l is active, some tags that should output clean URLs are returning the messy one. For example, txp:section_list.
Anyway, I’m not here to report findings (yet) but to ask for any advice-in-advance on using MLP + gbp_p_l that you or any other user may know.
So, here are some questions:
1) regarding plugin load order, what should come first? I usually load gbp_admin_library + MLP first (order=1, as suggested on MLP thread). Wonder if gbp_p_l should be loaded before or after them.
2) Once everything is set up and ready to start creating gbp_p_l rules, I wonder if you have any basic tips for the rules to work, being that MLP already rewrites them to include the lang chunk (ie. /en/, /es/, /fr/, etc). Shall those chunks be included in the gbp_p_l rules I create? If so, how? As text? or better as a regex?
Thanks.
Offline
#504 2009-10-31 21:51:48
Re: gbp_permanent_links
So far, I’ve noticed that when gbp_p_l is active, some tags that should output clean URLs are returning the messy one. For example, txp:section_list.
Mmmm, this happens with or withouth MLP activated. I can’t understand why. If plugin is enabled, most built-in tags that generate links (<txp:section>, <txp:section_list>, <txp:file_download_link>, etc), are generating them using messy URLs.
This plugin is so indomitable. The only person I know that tamed this beast is pieman, and he taught me a few good tricks.
Last edited by maniqui (2009-10-31 22:04:42)
Offline
#505 2009-10-31 21:55:58
Re: gbp_permanent_links
This might not be relevant, but of late (perhaps it’s a 4.2.0 thing) I’ve found it necessary to set the default Txp url prefs to messy, then override them all with gbp_pl. For reasons I haven’t figured, a combination of clean Txp url prefs and gbp_pl seems to produce unwanted results.
Offline
#506 2009-10-31 22:16:40
Re: gbp_permanent_links
Hi Maese Pieman,
thanks for chiming in and share your knowledge.
I see that on 6of3 (running on 4.2.0), preference is set to /section/title, but as we have created a lot of rules maybe we have covered every situation where a messy URL could appear…
As I’m using MLP, it seems that setting url prefs to messy is not an option. I’ve found that I can “fix” some of this messy URLs by just wrapping the output in <txp:gbp_disable_permlinks></txp:gbp_disable_permlinks>.
Another solution that I can apply on many places is to recreate clean URLs using chunks of information that can be rendered by TXP tags.
For example, instead of:
Browse article on <txp:section>this section</txp:section>
(which would output a messy link)
I can do:
Browse articles on <a href="/<txp:section>">this section</a>
(which is clean)
Of course, it’s a lot more of work, and having MLP in the middle doesn’t really help :)
Offline
#507 2009-11-02 01:34:06
Re: gbp_permanent_links
Another thing to report:
I’m developing a site tha runs on “Testing” mode. Thankfully, I’m not getting any kind of notices nor errors messages.
Until I create the first gbp_p_l rule.
Then, my install begins to show this kind of error messages on the front end
Tag error: <txp:title /> -> Textpattern Notice: Article tags cannot be used outside an article context on line 2175
Tag error: <txp:if_custom_field name="files"> -> Textpattern Notice: Article tags cannot be used outside an article context on line 2175
(this is just an example of the).
Not sure what’s going on, but again, after creating a gbp_p_l rule, those errors are “un-silenced” and begin showing on the front-end.
Any ideas of what could be going on?
Offline
#508 2009-11-02 03:34:26
Re: gbp_permanent_links
Maese pieman, maese graeme et all,
after fighting a little with gbp_p_l, once of those unexplainable miracles happened. Things just started to work. This is not the first time that it happened, now I remember than on previous TXP + gbp_p_l installs, it already happened to me.
It’s like there is after doing something (not sure yet what), gbp_p_l begins to behave.
Remember my two issues reported above?
- messy URLs being output on built-in tags (like section_list, section, file_download, etc)
- error messages appearing “un-muted” after creating a permanent link rule
Well, both magically disappeared.
What did I do to fix it? Not sure. I think it was switching from a clean URLs scheme to messy URLs (on Admin -> Preferences) and then switching back to a clean URLs scheme. I think that was the thing that triggered the miracle, as now I remember that on other ocassion, that fixed it too.
It’s like gbp_p_l has to “compile” something before starting to work properly.
Hope this helps anyone else.
Offline
#509 2009-11-02 03:46:34
Re: gbp_permanent_links
BTW, one minor thing regarding file downloads URLs.
I’m not sure since when (since which TXP version, I think it was 4.2.0) file download URLs have the filename appended to them.
Like this: /file_download/123/my_file.ext.
A nifty addition that may not only improve usability but also maybe it earns some extra SEO points.
Now, I’ve noticed that gbp_p_l “reverts” those URLs to the old ones. In other words, txp:file_download_link in tandem with gbp_p_l will return the “old version”, for example: /file_download/123.
Not that bad, as the URL is fully functional (the file can be downloaded without a glitch).
@graeme, do you think there is a chance to “fix” this?
In the meanwhile, I’ll keep crafting my file URLs from each chunk of information (file_download_id, file_download_name, etc) provided by TXP.
Thanks.
Offline
#510 2009-11-02 16:19:20
Re: gbp_permanent_links
maniqui wrote:
In the meanwhile, I’ll keep crafting my file URLs from each chunk of information (file_download_id, file_download_name, etc) provided by TXP.
Maniqui, it might reassure you to know that I’ve just experienced similar problems as you reported yesterday
Used in the News section, this returns the gbp_pl defined (section/yyyy/mm/dd/title) url:
<txp:article_custom section="news"><a href="<txp:permlink />" rel="bookmark"><txp:title /></a></txp:article_custom>
But used in any other section, exactly the same code returns a /section/title url instead – even though I have prefs=messy (!)
Had to build it manually with /news/<txp:posted format="%Y" />/<txp:posted format="%m" />/<txp:posted format="%e" />/<txp:article_url_title />
Don’t have time to do any further diagnosis at the mo, will try and get to the bottom of it soon.
Offline