Just found the time to upload this.
in admin.php?op=nukeSEOmeta under the second field of Select Keyword

I have \n";">\n";">';">\n";">\n";">\n";">\n";">\n";">\n";">\n";">\n";">\n";">\n";">\n";"

For what is the second field ? Is there an example somewhere `?
And what means the priority 0,1,2 ?

/admin.php?op=nukeSEOmeta&seofunc=keywordupdate gives me a blank page.


edit: I think I have to uninstall this completely because my page is now blank.



I usally optimize by hand and its hard to change the behavior but maybe I can figure it out somewhere.

Btw: I´m looking for a sitemap only for my forum. I could install a lofi version or a sitemap. Where would I find a sitemap only for the forum ?

Produced a Parse error: syntax error, unexpected $end in /www/xx/includes/meta.php on line 46.

Bad thing. I should better tried this first on a testsite.

Cause its now all in meta2 I quess I only have to rename meta2 to meta.php and remove afterthat the files. Need to get back my page.

Hopefully, this was answered on Raven's site, but just in case someone else sees this here first:
- remove both meta.php and meta2.php from the includes directory
- copy meta2.php from your download distribution to the includes directory and rename to meta.php
- copy meta2.php again to your includes directory
- make both meta.php and meta2.php writeable (set permissions to 0777).
- Go to admin and change your met tags, then save and you should be set
_________________

Thanks ! The sitemap works really great.
I did exactly what you said and I don´t have a parse error anymore but the meta thing doesn´t work on my site.

Within the log I found:

Table 'xyz.nuke_tuto_infos' doesn't exist
SQL was: SELECT "1" FROM nuke_tuto_infos

Table 'xyz.nuke_fancynl_archives' doesn't exist
SQL was: SELECT "1" FROM nuke_fancynl_archives

For what are these tables required ?

Quote:

Content-Type not been validated as no validation rules have been coded EXPIRES not been validated as no validation rules have been coded RESOURCE-TYPE not been validated as no validation rules have been coded DISTRIBUTION not been validated as no validation rules have been coded AUTHOR not been validated as no validation rules have been coded COPYRIGHT not been validated as no validation rules have been coded REVISIT-AFTER not been validated as no validation rules have been coded RATING not been validated as no validation rules have been coded GENERATOR not been validated as no validation rules have been coded

Doesn´t matter what I add there chmod is 777 it doesn´t work.Using Tidy it produced 14 new errors.

For the most ist will work unproblematic I´m quite sure.

Susann wrote:

... the meta thing doesn´t work on my site.

Are the changes not being saved?

Susann wrote:

Within the log I found: Table 'xyz.nuke_tuto_infos' doesn't exist SQL was: SELECT "1" FROM nuke_tuto_infos Table 'xyz.nuke_fancynl_archives' doesn't exist SQL was: SELECT "1" FROM nuke_fancynl_archives For what are these tables required ?

There are content classes for the Fancy Newsletters and Tutoriaux modules, and these are checking to see if the modules are installed. It doesn't hurt anything, but you can simply remove those modules from the modules/Sitemap/content folder and the messages will stop appearing in the log.

Susann wrote:

Quote: Content-Type not been validated as no validation rules have been coded EXPIRES not been validated as no validation rules have been coded RESOURCE-TYPE not been validated as no validation rules have been coded DISTRIBUTION not been validated as no validation rules have been coded AUTHOR not been validated as no validation rules have been coded COPYRIGHT not been validated as no validation rules have been coded REVISIT-AFTER not been validated as no validation rules have been coded RATING not been validated as no validation rules have been coded GENERATOR not been validated as no validation rules have been coded

These are warnings, not errors, and do not affect the operation of the module.

Susann wrote:

Doesn´t matter what I add there chmod is 777 it doesn´t work.Using Tidy it produced 14 new errors.

I'm not sure if the chmod reference means that it isn't saving, or if you get the warning messages above. At any rate, you should be able to save. Regarding the HTML errors, there is quite a bit of work to do on making it compliant. I'll make sure it's compliant in the next release.