English > Development

PK's MovieDB dynamic website template

<< < (4/17) > >>

rick.ca:
Looks good. Nice having all those sort options too.

I notice for many movies the actors are sorted backwards (i.e., from their IMDb credits order) so the lead actors/stars do not appear as stars in the summary.

This post describes my method of renaming poster files. It's probably not as convenient as the magic you're looking for, but you could adapt it to get the job done.

blue334:
The credits sorting is a problem with my database, not with the template. It was probably caused by the AMC import plugin (only imported records have the problem).

I suppose your method would make it possible to rename image files, but it may not be worth the hassle in my case. Uploading the full set of image files with every update may be time-consuming, but fortunately only for my ftp client.

blue334:
Another question: I mentioned in my top post that my free host awardspace.com have a list of filtered words/phrases. If a page rendered contain any of these words/phrases, you are redirected to their homepage. This is quite annoying, but I can understand why a free service has to discourage commercial/phishing/porn sites on their servers. Unfortunately, in imdb movie descriptions these words and phrases will pop up occasionally.

Several of these words/phrases are known, and I want to make automatic string replacement of filtered words an optional addition to the export template. The only problem is the replace function is case sensitive, meaning replace="fake id<->f ake id" works, but not if it contains uppercase (Fake ID, Fake id, Fake Id etc.).

Provided it is possible to change this, would it matter to other uses of the replace function if it was made case insensitive?

rick.ca:
I have no idea, but I imagine this function ultimately uses the Firebird SQL equivalent which happens to be case sensitive. I recall having a similar question... Perhaps nostra will answer both by explaining how replace works. My interest, generally, is using it to "clean up" imported data (by exporting and re-importing)—but replace doesn't help much with these limitations.

nostra:
The export plugin just receives data from the main application and puts this data into a file replacing variables in templates, so it has nothing to do with SQL.
The replace function is indeed case sensitive now, but I can change this behavior easily.

Navigation

[0] Message Index

[#] Next page

[*] Previous page