vivek

Forum Replies Created

Viewing 15 posts - 31 through 45 (of 239 total)
  • Author
    Posts
  • in reply to: 'Featured' default value #530356

    vivek
    Full Member
    Post count: 246

    Got it. Thanks very much for this, Alex

    in reply to: Claim – change in package/expiry #530355

    vivek
    Full Member
    Post count: 246
    This reply has been marked as private.
    in reply to: 'Featured' default value #530290

    vivek
    Full Member
    Post count: 246

    Hi, im still trying to get this to work as i want to – but no success yet.

    I understand that the Pricing Mgr overrrides the ‘admin only’ setting in custom field. So even though i have set admin only = Y, and Default = Unchecked, but i have Featured set to show in Package A, it gets set to checked – ie the default is also overriden automatically. If i set it not to show in package A, then it does not show at all and hence even if admin wants to show the verified badge they cannot do it.

    I want to use the badge as verified after some address/business documents are verified, hence default is unchecked, admin only and show on package (because i do want the badge to show after admin verifies the doc)? Hence checked and show should be 2 different things, rather than one thing. And i do wnat to use pricing manager because i have multiple packs – free, paid (M,Q,A).

    How can i achieve this please, without having to manually uncheck the box while publishing each listing?

    thanks,
    Vivek

    in reply to: Claim – change in package/expiry #530257

    vivek
    Full Member
    Post count: 246

    Hi – just checking if there is any update on this thread. thanks

    in reply to: 'Featured' default value #526862

    vivek
    Full Member
    Post count: 246

    Hi Alex- exactly, i am setting the Featured to default as “UNCHECKED” in the settings, yet when a new listing is created, the box is checked and then i have to remove the check before approval. How do i make it such that the check is off by default?
    The creds are attached above so you can see the setting and add a new listing.
    thanks, Vivek

    in reply to: 'Featured' default value #526517

    vivek
    Full Member
    Post count: 246
    This reply has been marked as private.
    in reply to: Downgrade/ expire behaviour for inactive package? #525937

    vivek
    Full Member
    Post count: 246

    Thanks very much for clarification. The behaviour is then as expected. Pls close this one.

    in reply to: Downgrade/ expire behaviour for inactive package? #525693

    vivek
    Full Member
    Post count: 246

    “even if a package is inactive, if it has been applied through the frontend to a listing, then the settings of the package will still apply”

    Yes, here my query is about an ACTIVE package (PACKAGE 1), whose downgrade setting was PACKAGE 2, at the time the listing was created. Package 1 had a lifetime of 3 months, so after 3 months, the listing was downgraded to PACKAGE2 (now inactive)

    Inbetween the 0-3 month period, the downgrade setting of PACK1 (which is still active) was changed from PACK2 to EXPIRE, so should the listing have expired or should it be downgraded to PACK2?

    in reply to: Renewal/upgrade email on admin actions? #525690

    vivek
    Full Member
    Post count: 246

    SO in this case, the listing had downgraded to an inactive, non-recurring, non-expiring, free package, and then from admin, I changed the package to an active, non-recurring, free but 3 month lifetime package (same pack as it was earlier in before expiry)

    In this case i observed the following:

    1. User/admin bcc for renewal or upgrade were not sent- possibly because the previous package was infinite lifetime and non-upgradeable- I just changed the package in admin and saved. – is this right?
    2. After saving with the new package, in export, the listing shows the new package, but with 0000-00-00 expiry, so it is not setting the expiry date for 3 months hence – is this also expected?

    in reply to: Understandting requests from GD to google maps #523996

    vivek
    Full Member
    Post count: 246

    Also is PLACES API used anywhere? I am seeing some requests for Atmosphere Data, Contact Data, Places without autocomplete… are these required by GD, and if not, is it possible to disable Places API in the account to avoid misuse?

    in reply to: Getting 404 on wpi-checkout page #523255

    vivek
    Full Member
    Post count: 246

    Yes, Alex- I have the test gateway enabled, and all the other packages i am using on the site are free so it doesnt go to gateways anyway, only this package (13 in gd_compt_coaching) sent above, i had created for testing again with a price, so that is going to invoicing and resulting in 404.

    I have removed the browser pass so you should be able to access it

    thanks,Vivek

    in reply to: Getting 404 on wpi-checkout page #523253

    vivek
    Full Member
    Post count: 246

    Thanks, Alex. I do understand that the PG should be added, however since I was only testing i was surprised to see the 404 – particularly since i have previously made dozens of checkouts with “Test Payments” , without encountering this 404, while testing a few months ago.

    Hence i wanted to understand if something has changed that wpi-checkout was working with test payment earlier and has now stopped working?

    thanks,
    Vivek

    in reply to: Getting 404 on wpi-checkout page #523193

    vivek
    Full Member
    Post count: 246
    This reply has been marked as private.
    in reply to: GD recaptcha issue – unable to login #522693

    vivek
    Full Member
    Post count: 246
    in reply to: Errors after update to 2.0.70 #521473

    vivek
    Full Member
    Post count: 246

    Sorry- this probably had nothing to do with GD update, but rather concurrent WP update to 5.3.1.

    I guess i will just hide the PHP errors in wp_config.php

    thanks,
    Vivek

Viewing 15 posts - 31 through 45 (of 239 total)