Thread: Classifieds trouble

I understand the new logic - stays 'til expiration, but expiration is not visible. Is it possible to find the expiration of the 'sold' items? Can they be edited?

There is no interface in the software that I've found providing access to the 'expiration'.
If you want to join the Dev team and read through and understand the actual programming code, you can probably find out when the ads stop counting and fix it. I know how I want the software to work, but actually spending the time to make it do so is not something I can afford at present.

I understand the logic w/ counts and expiration.

But expiration isn't showing, much less editable. Is there a way to find out how long the wait will be? 'Preferable be able to edit it?

Nope. Chuck Tester.

One post suggests searching the archives would display the ad expiration, is there a method that returns results reliably? 'Just tried by search, and by scrolling through archives.

Originally Posted by pinklather

One post suggests searching the archives would display the ad expiration, is there a method that returns results reliably? 'Just tried by search, and by scrolling through archives.

As Chuck said , 'Nope'
The only way I can see to set an expiration is when first placing the ad. If you set the ad for 90 days... bad move.

Originally Posted by onimaru55

As Chuck said , 'Nope'
The only way I can see to set an expiration is when first placing the ad. If you set the ad for 90 days... bad move.

I agree. When one sets an ad to expire at a given date, one has to expect the ad may (worst-case?) be listed for that entire period. So plan accordingly

Originally Posted by gugi

There is no interface in the software that I've found providing access to the 'expiration'.
If you want to join the Dev team and read through and understand the actual programming code, you can probably find out when the ads stop counting and fix it. I know how I want the software to work, but actually spending the time to make it do so is not something I can afford at present.

What's the code written in?

If the back end is SQL, it would seem a few update statements could get guys out of the hole who had 90day expirations in place when the last revision was made.

The code is php, the problem is that you have to understand the logic of the counting when determining which ads count and which don't towards the total allowed (after you find where it happens, how the status update works etc.). It's not just a matter of a simple update of one number in a table.
I have looked at it briefly to get an idea what it looks like and it's not a project I am taking at this point.

Hi Gugi,

I'm illiterate in php. 'Don't know if its very human-readable. I understand how the logic must be comprehended. Gremlins have a way of breaking things elsewhere when you try to fix someplace else.

A good question would be if a stored proc that executed upon marking 'sold' could play nice w/ the logic that counts for the sake of status. If the counting logic doesn't care that a new value is held - just uses it, the update (sold) function could be the only place any a change had to occur. (upon 'sold', set expiration date to sysdate + 1) 'Makes me wish I was closer to the devs, and or the code to be able to do some lifting on the effort.

Either way, I appreciate your kind effort, and that of the other devs. 'Seems an unfortunate change of business rules (in the code) that have caught a number of us in pita situation. You guys have GOT to be really tired of hearing about it. Hang in there.