Moderator: Coranto Moderator Team
Normally one do not specify the output file name when submitting a news item (this is done in a profile) so we really need more info about your setup to understand what might be causing this.YushDon wrote:I've discovered that if I successfully submit an entry using version 1.31.4, then go back to modify that entry but change the filename, it just doesn't recognise the new filename. It simply reproduce the old filename for that document no matter if I do a full or partial rebuild.
I've even tried deleting the file generated in the location specified by the profile, but it again reproduces the old filename. This does not happen in the stable version 1.24.
Well, I said *normally* this is not the case and in order to understand what causes YushDon's specific problem more info is really needed about his setup. Do you experience problems with your setup as well?shanemckiness wrote:I submit a new filename with each new article, this way I can create a true custom address with name relavant to the article without the headaches of using the subject field (or any other field). So I understand what he is going through.
Do you use the CSQL addon and 1.31.x? If so, that is fairly untested (and unsuported) territory (even with Coranto 1.24). Please try without it...YushDon wrote:My set up is fairly basic: I've got 1.31.4 running on a Linux box using Fedora, php 4.31, mySQL 3.23 and the latest perl with DBI and other required modules.
And the output file is created how? Just by having a field named CustomField_FileName doesn't automatically create a file, more details please...YushDon wrote:I have created a custom field called CustomField_FileName into which I type my own custom name of each file (or article) that I submit. On ver 1.24 I can change this filename and at build time the process will either generate a new filename or update the old one.
I thought it was something like this you had setup, but if you read your first post in this thread again, you see that you do not mention anything about using Maginot. When you report about a problem, especially since you are testing out Coranto 1.31.x, you need to give the complete and accurate picture so there is no misstakes about which parts are involved. OK?YushDon wrote:I created the output file using a Maginot profile which split the output along the CustomField_FileName I created. I then chose the output extension as php. When I run build (either full or partial) it would then create documents which look something like this:-
http://www .mywebsite.com/outputfolder/<Field: CustomField_FileName>.php
:confused2:YushDon wrote:I have tried to duplicate the same situation with version 1.31.4 but now I think I may have discovered why the document does not update or create a new file: I have not created a Maginot profile!
I have been using a standard profile with it all this time. I will create a Maginot profile and see how I get on with that, then report my findings.
Well, do not look at me about the CSQL problems, that is Lawrence show...YushDon wrote:What would be good though is if I could get csql to work without giving me the error mentioned here. Then I could really push the system because all of my content revolves around the existence of csql.
shanemckiness wrote:I usually never change my filename, but on occasion I did, and everything worked just fine. I am use 1.24 though without sql.
Does an old copy of the file with the old filename remain after you do this? I'm interested in using this solution but am concerned about running into such problems.
Users browsing this forum: No registered users and 2 guests