AbleDesign

[bongo]

Hi,

I added 6 fields using the instructions outlined in the thread "Instructions for adding a field & making it show on myca", but had some trouble making the new fields show up properly when the event is submitted and the screen shows the submitter the information they submitted. Everything gets submitted properly and goes into the calendar_Validate table, etc., it's only having a problem displaying the new fields in this one page.

I narrowed it down to the add_to_validate.php page in the "display the submitted event to the user" section. I had copied and pasted the "title" row, and modified the field name to match the field name in the db, so that it read:

[Dan]

Is your 'where' field a textarea input form element that can contain multiple lines of text? If so, that could explain what you're seeing.

I'm not sure off hand why not converting to newline breaks on a field that requires it would keep things from showing up, though. Seems it would just run all the lines together. Where you're using $where, did you assign that value from $db_validate[V_WHERE_ROW][2] like is done for $description?

Cheers,
Dan

[bongo]

Only the $description is set up to have multiple lines of input.

The description has the format

[Dan]

I don't know which MyCalendar version you're using, but you should see the following around line 75 in add_to_validate.php:

$description = $db_validate[V_DESCRIPTION_ROW][2];

and right below it:

$db_validate[V_DESCRIPTION_ROW][2] = nl2br($db_validate[V_DESCRIPTION_ROW][2]);

One is for displaying what has been submitted, the other is for updating the database. (I split the two up to avoid re-processing the already processed data for the confirmation.)

[bongo]

I'm using 2_20_b4. The $db_validate wasn't in that line, and there's only one line. I just checked my original, unmodified file to make sure I hadn't inadvertantly mutilated it in my attempts to get it to work!

Could that be the problem then? Perhaps if that line is missing, it's bombing at that line because it's expecting something that isn't there? If the line in my file only reads (nl2br($description)), and (nl2br($where)), how is it populating the fields on the user-submission readout? Would that be simply returning the last-known value for that variable?

Should I put the two lines you listed below into add_to_validate.php (and also for $where)?

Thanks,

[bongo]

I see it now, it's farther up than the section I was referring to. My bad.

Should I put in a similar section for each of the new fields I put in?

[Dan]

You shouldn't need to add that in unless it is a multi-line field like Description. That section up above is for things like formatting the description, assembling the day from the month/day/year components, calculating the day of week, etc. Unless your added field fits any such non-standard criteria, the only explanation I can think of for the behavior you're reporting is a minor error somewhere in your customization.

Cheers,
Dan

[bongo]

Okay. Can you think of any reason why I should NOT leave it like this, even though the $where isn't like the others, and there is no $db_validate line for it anywhere? It works, but I don't know PHP enough to know if it will cause any problems.

[Dan]

Well, I never like leaving anything as is that I know isn't working properly, but if you're sure it is getting properly submitted to the Validate table and admin validation of the event works just fine, then it may not be worth worrying about something that is only a confirmation display.

Cheers,
Dan

[bongo]

I'm the same way. I'll check out allof my other files that I modified and see if I configured something goofy somewhere.

Thanks for all your help! This program is awesome, and the support has been the best of any program I've ever bought! The only problems I've had so far are due to me trying to customize it.

bongo.

[Dan]

Thanks for the nice feedback.

[bongo]

I know. I began thinking of how to write a shell script to ask for the field name and automate putting it in all of the required places, but then just trying to figure out how to have it put it in with the correct numbers in config.php made my head hurt.

Great job, though. I know all you read in the forum is the problems people are having. I hope you get complimentary email, because the program is great.

bongo

[Dan]

Don't suppose you'd be interested in writing up a testimonial based on the above comments?

[bongo]

Sure, I think it's a great program!

I think if only an administrator has access to the files anyway, and they run the script, what's the difference if they run the script as owner or if they hand modify the files as owner? Maybe have the script make the files writable, do the deeds, then reset permissions again before moving on to the next file.

...just a thought... If I come up with something that works for me I'll email it to you.

[Dan]

That's a good point. Assuming your PHP setup allows you to change file permissions on the fly (not a safe assumption, as mine doesn't, presumably due to safe mode), that would provide a good way of protecting the script that is allowed to set write permissions.

Cheers,
Dan