Forum Replies Created

Viewing 13 replies - 1 through 13 (of 13 total)
  • Thread Starter iret1

    (@iret1)

    IT WORKED!!!! Thank you very much. Great plugin. Great support. I REALLY appreciate your help! I’m in a hurry to leave 5 stars for your plugin.

    Thread Starter iret1

    (@iret1)

    THANK YOU VERY MUCH! All is good now. I sincerely appreciate your help. I’ll be leaving your plugin a glowing review in a couple of days.
    Best regards,

    Thread Starter iret1

    (@iret1)

    I appreciate your fast response: thank you! Just one question, if access is denied to all and a song is sold, will the customer be able to download the song he paid for?
    Great plugin. Great support. Best regards.

    Thank you, Redymedan!
    I followed your advice too and yes, it worked. You are brilliant! I felt quite lost without CRP and I sincerely appreciate your help.

    I have the exact same problem!
    I’m using Contextual Related Posts for several years on several Websites and the plugin was always FANTASTIC!
    I know that WordPress does many updates automatically now and following one of them – on ONE of my Websites – Contextual Related Posts plugin produced a fatal error which is why I had to delete it.
    The error: Fatal error: Can’t use function return value in write context in /………/……../public_html/wp-content/plugins/contextual-related-posts/includes/content.php on line 66
    How I tried to fix the problem: I downloaded the latest version of the plugin from WordPress to my pc and compared lines 66 of both files, the one I had to delete and the brand new download. They were identical!
    I tried to download Contextual Related Posts through my self-hosted Website’s WP admin, but the plugin couldn’t be activated because activation attempts cause fatal error.
    I’m using the latest version of WordPress and was using the latest version of Contextual Related Posts.
    Any suggestions? I REALLY miss the plugin!

    iret1

    (@iret1)

    The same problem as everyone above and persisting for the past 3 days. I cleared cache and made sure that my Website is listed on WordPress, it is. Now what?

    Thread Starter iret1

    (@iret1)

    Developers of BePro Listings avoid providing direct answers and there are several valid reasons for it.
    In my case, as described above, a truthful answer – I found it myself by way of VERY HARD LABOR, each stage documented with screenshots!!! – would have discouraged many from getting involved with the plugin. The correct answer is: if you’re planning to charge and want to prepopulate listings in order to encourage sales, DO NOT USE BePro Listings’ PLUGIN! It can’t be done. Your initial listings will really be “around” (NOT IN!) and useless.
    The expiration date you can – yeah right! – set on the admin side, DOESN’T WORK. By default, the moment you touch ANY listing (your own OR customer’s) the listing will NEVER expire.
    Shortcodes – an important part of any directory’s software – included with BEPro Listings (except of the three initial ones which are part of the installation) are DYSFUNCTIONAL.
    In a nutshell, BePro Listings is a BAD quality plugin WITHOUT developer’s support. In fact, it’s a ruse. The premise of the plugin is attractive. As soon as you install it, you’ll find problems. When you ask for support, you’re told to register on the developer’s private forum. (A friend of mine is a member, I’ve seen it.) There is no help to be received on the private forum either: most questions are answered with: “we provide PAID support” and “there are PAID add-ons” for just about everything. Incidentally, the add-ons are HORRIBLE and have as many problems as the plugin! Even if you buy them, there is NO support for the bought items, either unless – of course! – you pay for it. The funny part? Many people who ask for help on the private forum list their URLs. I didn’t find ONE that currently uses this plugin…..)
    CONCLUSION? If you’re planning any kind of directory, DON’T USE BePro Listings plugin. You’ll be dismayed, disappointed and very sorry if you do.
    TO THE DEVELOPER: I don’t need any more help, thanks!

    Thread Starter iret1

    (@iret1)

    UPDATE: I’ve taken screenshots of “My Listings” page in free and paid mode.
    In the free mode (when the listings “act” normally within the Website): Notices: None; Status: Published.
    When I switch to the paid mode (when the listings “act” weirdly within the Website): my ads are Pending: PAYMENT REQUIRED! Notices: Expires: Never; Status: Published.

    QUESTION: is this what you mean by “around”? Meaning somewhere in the system but – unless I make a payment! – INVISIBLE in [bl_all_in_one], in search and in [display_listings]?

    As you see, I’m really trying to make things work. I invested (wasted?) a lot of work and time. It would be nice to receive a clear yes or no answer.
    What’s your definition of “around”? The exact problem I’m stuck with? Yes? No?

    Thread Starter iret1

    (@iret1)

    I appreciate the fact that you replied but how about some actual answers to my questions?

    1/ Can free and paid ads appear SIMULTANEOUSLY together in display, searches, categories, etc.? (“Be around” is neither precise nor helpful. My free listings are “around” right now: it’s a disaster!)
    2/ Why are my free, published listings present in BePro Recent Listings widgets and INVISIBLE in [bl_all_in_one] and in [display_listings]? (You said: “Listings may not show up after submission for a range of reasons e.g. their status is draft”. As I clearly stated in the question: the listings are PUBLISHED and show in BePro Recent Listings widget and categories, drafts wouldn’t.) Can you please name a reason that would apply to my situation?
    3/ Why expiration date set on the admin side is NEVER even though there is a calendar option where I’m setting a specific date? (Plugin malfunction?)

    I’d be grateful for replies to my specific questions. Your original reply didn’t address any of them.

    Thread Starter iret1

    (@iret1)

    Hey Barry,
    Thank you for your reply. I understand, of course. I regret however that even though I’ve been clear from the beginning that in the US we list the year of a car’s model as opposed to the car’s first registration date, you didn’t let me know one week ago that modifying the input field of your plugin’s submission form isn’t possible. I’m sorry I wasted so much work….
    Cheers,
    iret1

    Thread Starter iret1

    (@iret1)

    Hello Barry,
    Thank you very much for your continuing support! I tried the new snippet. It didn’t result in a syntax error. But it didn’t produce the desired outcome, either. It replaced First Registration Date with My First Registration Date Replacement. I tinkered and arrived at the much wanted YEAR. Unfortunately, the user is still required to provide year, month and day in the input field… Isn’t there a way to replace the input field with a BLANK one like the Listing Title, for instance?
    The way it was and the way it still is, the user is REQUIRED to lie or walk away….
    I sincerely apologize for being so persistent. I really think that your plugin is terrific and I’m not ready to give up on it.

    Thread Starter iret1

    (@iret1)

    I sincerely appreciate your help and the effort you put forth. The second part of your advice (in regard to the word “optional”) worked immediately and solved my problem.
    Unfortunately, the first (in regard to changing First Registration Date to Year, only) failed. I crashed my Site 4 times, no matter what I did my Website consistently returns: “Parse error: syntax error, unexpected ‘}’ in functions.php”. I used the code you provided, EXACTLY. I didn’t forget to close the code. I tried to mimic my theme’s functions.php formatting (/** and */). I tried already everything I can think of to make the snippet work but it doesn’t. I’m using the Suffusion theme. Any advice? (The reason the change I requested is so badly needed is that in the United States, we don’t know the date of the first registration of our cars; we know the car model’s year.)
    I love your plugin and REALLY want to make it work for me.

    Thread Starter iret1

    (@iret1)

    The fault was mine, it’s solved and it had NO bearing on your plugin! Please accept my apology.

Viewing 13 replies - 1 through 13 (of 13 total)