iwoaw
Forum Replies Created
-
Posts
-
This reply has been marked as private.This reply has been marked as private.This reply has been marked as private.This reply has been marked as private.This reply has been marked as private.
Quick follow up question. How can you delete blanks with just an ID number and categories? I don’t see them in WordPress (no titles). Would deleting the row in the csv and re-import do the trick?
blank…. thanks for the time saving tip, Guust.
Yes, that’s what I meant. That’s too bad 🙁
Thanks.Also, I just noticed something new… there is “–> –> –>” added after the ads everywhere except for the front page. The ad invocation code doesn’t change and doesn’t include text after the ad.
Do you know where that is coming from?
Thanks. I’m having trouble with the front page widgets… One of the ‘best of’ doesn’t show the tabs and the listing sliders that are supposed to show the ‘featured’ listings do not. Any ideas why?
Everything was properly selected and working before the update.
Yes, I thought it was saved in the database which is why I was surprised that the labels were removed during the update process for ‘events’ but not the other types including ‘places’. Apparently, it took the settings away too apparently.
I basically updated the core then proceeded to update the plugins.
This reply has been marked as private.I changed text to img. The certification seal at the top of detail page looks great! Thank you so much.
The issue is that I currently have 4 different packages for different post with different field adjustments, duration, and featured-status and that after being told I could simply apply a package in the back end, the same it is possible to do in the front end, it turns out that I have to spend significant time going at it one field (one setting at a time) after sorting through to find the correct.
Yes, doing that in the database will be a little faster but it is overall painfully labor intensive and I don’t understand why it has to be that way. I don’t understand why packages can only be activated from by end users and but not admin. It is a surprising design choice.
Don’t get me wrong, I’m truly impressed overall but this one is disappointing as it is so administrator unfriendly and business model restrictive.
I understand that everything works in the backend, just not as a package. Is that correct?
We are dealing with thousands. Manual input of featured-status, duration, field limits, etc. for each applicable listing is not time reasonable.
Does that mean that there is no point in having the price packages as they won’t work (set the specific features for the given listings) in the back end or through an upload? We don’t need an extra thing if it won’t do anything for us.
