Hi all,
I just upgraded one of my sites to the latest version of phpwcms.
I really like the keyword function to render extra content. (e.g. a right bar with teasers based on keywords, this might be usefull too).
Unfortunately keywords don't seem to work in the newest version.
Also when I'm filling the keywords there appears an autofill list, when I click a keyword it fills 'undefined'.
Is there something I have to change or is it a bug in phpwcms?
Besides this /bug I am a big fan of phpwcms! Thumbs up!
Hope to get an answer..
Problem with article tags / keywords autofill in 1.4.7
- Oliver Georgi
- Site Admin
- Posts: 9892
- Joined: Fri 3. Oct 2003, 22:22
- Contact:
Re: Problem with article tags / keywords autofill in 1.4.7
It seems there are some files missed. "Undefined" comes from JavaScript. So check if all was updated well or JavaScript is not blocked.
Re: Problem with article tags / keywords autofill in 1.4.7
Thank you for the quick response.
The autofill problem is solved by using IE instead of Google Chrome.
Like I explained before I want to use the contentpart "teaser" to give a column with things that might be interesting too, based on keywords.
But when I put the teasertype on 'random' (because they might all be interesting except the ones that ares "sold") and type in the textfield tags the keyword that should NOT be selected, it still selects it. Check http://www.fhhorses.com/nieuw/paarden.phtml and click one of the horses to see what I mean. (it's in Dutch, but okay) The horse Bordeaux is sold so there's a tag in the article "verkocht". Still it appears sometimes in the list in {RIGHT} with possibly interesting horses.
Hope you can help me with this.
Michiel
The autofill problem is solved by using IE instead of Google Chrome.
Like I explained before I want to use the contentpart "teaser" to give a column with things that might be interesting too, based on keywords.
But when I put the teasertype on 'random' (because they might all be interesting except the ones that ares "sold") and type in the textfield tags the keyword that should NOT be selected, it still selects it. Check http://www.fhhorses.com/nieuw/paarden.phtml and click one of the horses to see what I mean. (it's in Dutch, but okay) The horse Bordeaux is sold so there's a tag in the article "verkocht". Still it appears sometimes in the list in {RIGHT} with possibly interesting horses.
Hope you can help me with this.
Michiel
- Oliver Georgi
- Site Admin
- Posts: 9892
- Joined: Fri 3. Oct 2003, 22:22
- Contact:
Re: Problem with article tags / keywords autofill in 1.4.7
It might fail because your article has more than 1 keyword.
Re: Problem with article tags / keywords autofill in 1.4.7
Hi Oliver,
I think you are right. I've removed all the other tags in the article and now after more than 20 refreshes, it's not showing up anymore.
Thank you very much!
I think you are right. I've removed all the other tags in the article and now after more than 20 refreshes, it's not showing up anymore.
Thank you very much!
Re: Problem with article tags / keywords autofill in 1.4.7
Hey Oliver, this is still an issue.
Chrome does not support the Ajax funciton to insert keywords. It just displays "undefined". Any help on this? Since i love chrome, its not an option to change the browser while editing phpwcms.
Thanx in advance!
Chrome does not support the Ajax funciton to insert keywords. It just displays "undefined". Any help on this? Since i love chrome, its not an option to change the browser while editing phpwcms.
Thanx in advance!
2008
- Oliver Georgi
- Site Admin
- Posts: 9892
- Joined: Fri 3. Oct 2003, 22:22
- Contact:
Re: Problem with article tags / keywords autofill in 1.4.7
all newer browsers are broken, no time yet to fix it
OK I have fixed it. It happens for newer browser with — I have found a solution and the reasons is that newer browser like IE9 and FF4 introduce ECMA Script 5 which has native bind support. Add this on top of your MooTools 1.1.x library or download the attached file:
OK I have fixed it. It happens for newer browser with — I have found a solution and the reasons is that newer browser like IE9 and FF4 introduce ECMA Script 5 which has native bind support. Add this on top of your MooTools 1.1.x library or download the attached file:
Code: Select all
// Fix for MooTools 1.1.x and bind() related problems
try{delete Function.prototype.bind;}catch(e){}