Couple of issues - any help really appreciated

[Tiger]

Hi there,

I'm using Actinic Developer and I have a couple of knotty problems to solve, which try as I might, I don't seem to be able to at the moment. I wonder if anyone else out there can help with these two little gems....

Firstly, is there a way I can change the code:

<META NAME="ActinicKey" CONTENT="c98228447efb68b54d1446d67d2fbd580">
<META NAME="Generator" CONTENT="accxecom8">

Into:

<meta name="ActinicKey" content="c98228447efb68b54d1446d67d2fbd580" />
<meta name="Generator" content="accxecom8" />

Which is valid XHTML. It's making my pages fail validation at the moment.

The second problem is with the sitemap and it's a couple of things really.

Number one, is there a way of including the brochure pages in the site map listing as well as the shop sections? At the moment I've hard coded them in but it would be much nicer of they were automatically included. If this is a feature I've missed, what do I need to do to make it happen?

Number two, I know that the sitemap uses the default primary template (whatever I might set that to be) and I also know that the search page (and search results page) uses the same. I really need them to use different primary templates - is this possible and if so, how?

If anyone has any ideas on any of these things I would be exceptionately grateful.

Actinic support folk, feel free to jump in any time.....

Cheers,

Angi

[Tiger]

One of the problems now solved

Hello again,

Just to let you all know that I have solved one of the issues with the search template myself now by using server-side includes.

The rest still remain though, so if anyone can help, let me know.

Cheers,

Angi

[cdicken]

Number one, is there a way of including the brochure pages in the site map listing as well as the shop sections? At the moment I've hard coded them in but it would be much nicer of they were automatically included. If this is a feature I've missed, what do I need to do to make it happen?

It isn't a feature you've missed. I'm afraid I know no way to make this happen other than hard-coding the HTML into Act_SiteMap.html.

With regards to the <META> tags, I've had a good look but not found anything. I think this means it comes from the actual application and so cannot be edited easily. I can ask the development team for you - but I'm out now till next Tuesday so I won't be able to get back to you for a while.

[NormanRouxel]

Regarding the META tags. They are generated from the line

<!--@act NETQUOTEVAR:HEADERMETA -->

In Act_Primary.

And, yes, unfortunately they do come from the application.

A quick peek with a hex editor showed that these strings have a Carriage Return / Line Feed at the end so if were feeling brave and you didn't mind these tags appearing on the same line you could try patching catalog.exe.

Fixing the case is easy. Replace the "> CR LF" with "/> " - note trailing space to get the character count correct - we don't want an isolated Line Feed.

Norman

[Tiger]

How?

Cheers Norman. I'm more than happy to edit the catalog.exe file to make this work. What do I edit it with though?

Angi

[cdicken]

The source code is not available to edit.

I have asked the developers to change this in the next maintenance release.

[NormanRouxel]

You could patch the binary file catalog.exe with a hex editor; but this is really dangerous territory and I'd recommend waiting until the update Chris mentions comes out.

Norman

[Tiger]

The source code is not available to edit.

I have asked the developers to change this in the next maintenance release.

Thanks Chris (and Norman). How have you asked the development team to change it though? It would be best to make it available for alteration rather than just changing it. The reason I say this is that lowercase and with '/>' at the end is how I need it, but other people might need to have it in a different format.

[cdicken]

I have asked the developers to move them into 'Design | Text'. Trouble is, as this is a database change, it will not be in 7.0.2 (we don't want to put anything in 7.0.2 which will trigger any kind of upgrade). Expect to see it in a future maintenance release.