The module is not creating dynamic meta tags anymore
| Project: | Integrated Metatags |
| Version: | 6.x-1.0-beta4 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | fractile81 |
| Status: | closed |
Jump to:
Thanks for fixing the error that "combine" made under php4. not it works, and also the manual metatags entries do their job. But unfortunately, all the dynamic metatags (node.title etc) are not doing anything at all. I can activate them but they dont appear in the source code (and they really dont, i did not only refresh the site) May it also be because of php4?
Two more things i want to report, no just one in fact: i have fckeditor installed, and it is a big mess to put in the manual metatags. you have to choose "use simple text editor" and then work in there (with fck it adds all this html tags) and then after saving it works but if you want to change something you have make a big procedure to remove the
tags again, that automatically has been saved there. is it possible to just keep the fck module away from interfering with your module, would be good to exclude it.
#1
Alright, first there was a bug in the BETA3 release that accidentally destroyed your settings for each content type. Make sure to verify your settings, including that the types are enabled. After verifying your settings, let me know if you still have problems.
Second, it looks like the FCKEditor should have a setting where you can exclude certain forms from FCKEditor. Add the "edit-static" field to that, and it should stop showing.
Hope it all works out!
#2
thank you fractile, the fck is fixed.
the other problem is still there, i did not make an update but started from scratch, so i enabled IM itself, giving manual metatag entries there, and then also enabled it in the content-types, inheriting the manual tags. and it works so far. but if i add e.g. node.title, activating it, giving as name "keywords" (using combine or also not i tried both, also tried testnames), nothing appears in the given out source (and i also made sure that it is not a browser refreshment problem :)
i tried out now locally on php5 and here it works. so it is infact a php4 problem somewhere which hopefully is fixable.
thanks for your great work
sascha
#3
Do you have a sample link you can post that is having this problem?
#4
Also, it's worth mentioning that your page theme must be printing the $head variable for this module to work. What theme are you using?
#5
i checked the head variable it is there and working (also the manual tags are being putout into the source code)
i cant send you a sample, my site is www.engelwoche.de and as you can see in the source code, it generates the description, keywords metatags fine (they are generated by your module, general settings, manual tags and then inherited into page). but when i do add e.g. node.title, giving whatever name, using combine or not, it doesnt generate these variable ones, they dont appear in the code. i tried out with exactly the same site in local environment where i have php5, and here it does its job. so for sure it is just about the variable ones and it is about php4.
if i can help you with something more useful than a link to my site, if i should try out something just tell me...
#6
Have you tried updating to BETA4? Please update this issue if you have.
I'm trying to think of why this might be a problem for you. When you add the title in and the tags don't display, can you check Watchdog ("Recent log entries") to see if you're getting any PHP errors? Also, do your titles have any special characters in them (like an umlaut or ß)?
#7
I have the problem with the BETA4 too.
I tried also by making the CCK fields the module takes the content from visible to authenticated, and anonymous users, but the issue still shows.
#8
@Kiam: Are you also running in PHP4?
#9
Yes, I am using PHP4.
#10
Got it! It was an odd issue with how PHP4 doesn't handle pass-by-reference values the same way PHP5 does with the call_user_func(); function. I've removed this function since there are other ways of doing the same thing. This fix will be in BETA5, which will be out shortly.
#11
Oops, forgot to mark this as fixed.
#12
#13
Automatically closed -- issue fixed for two weeks with no activity.