Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter mattpr

    (@mattpr)

    Thanks for the quick reply.

    The site/home change was made before the site was launched. No pages, no posts, no images.

    Many of the errors are related to cross-site scripting issues…with wordpress javascript being loaded from the old domain rather than new domain.

    This change was made months ago and we just started working on the site…but I also did cache/cookie clearing just to make sure.

    I confirmed with mysql that the value in the database for siteurl and home were the old values and did not reflect what was in wp-config.php. ie the db never gets updated when values are set in wp-config.php. Then the problem arises because it seems that wp uses the db value instead of the value in wp-config?

    Updating these values manually in the database to the correct values resolved all the problems immediately.

    Hence I figure it is a bug of some sort. Would expect either:

    – if vars are set in wp-config.php, then db values are ignored or
    – db value is used globally, but when vars are set in wp-config.php the db value is updated.

    I am guessing most wp users are just setting this in the db via the Settings>General page…which I am guessing isn’t broken.

    One more thought… I am appending these defines to wp-config.php via my provisioning scripts. Perhaps being included after the require_once for wp-settings.php causes an issue? Maybe wordpress is functioning as expected and my defines just aren’t getting picked up from wp-config for some reason? I wouldn’t think the order of the defines in that file would matter so much but that would also explain it. On the other hand…the Settings>General page shows the home/siteurl boxes greyed out and shows the values from wp-config.php and not from the db. So still think there is something wrong here.

    
    /* ... */
    /** Sets up WordPress vars and included files. */
    require_once(ABSPATH . 'wp-settings.php');
    define('WP_HOME', 'http://www.example.com');
    
    define('WP_SITEURL', 'http://www.example.com');
    /* EOF */
    

    The original install was done with whatever the latest stable WP was on October 29. Just checked: 4.9.8. The domain change was shortly thereafter. I did the upgrade to 5.0.2 this week (from wp-admin UI) before we started developing the site content. So possible this is a bug from a pre5 release.

    Thread Starter mattpr

    (@mattpr)

    Hi Frederick,

    The biggest problem with the amazon associates link builder (once you have gotten over the hurdle of setting it up and fixing your CSS) is that if you want to edit a link/banner you have to start from scratch. The plugin embeds everything all the link/banner config into a shortcode and you can’t really edit that shortcode data within the link builder plugin…you would need to manually edit the shortcode text by hand or re-build your link from scratch. If you are only linking to single products in a single marketplace rebuilding each link instead of editing when you need to edit is probably not too bad. However if you carefully build banners with multiple products in multiple amazon marketplaces (e.g. US, UK, DE, etc) then it is a nightmare if you make a mistake and need to edit.

    If your primary market is the US, then amazon’s new “onelink” program might be better for you. Basically you embed a javascript library from amazon and then just link to US amazon store products. If a user is in a different country with a different amazon marketplace, then amazon will automatically send the user to the same (or similar) product in their own local marketplace.

    Downsides of onelink:
    – only works from US links for now meaning that the US needs to be your primary amazon store that most of your users are from. If you are international and linking to common international products you can probably work with this as well. However if you are linking to specialty products that are very different between regions this doesn’t work as well as manually selecting the specific products/ASINs from each market.
    – another javascript library on your site slowing down your page, leaking data to amazon and causing more overhead (think GDPR).
    – I don’t know how good the onelink guesses are when they pick products in other markets to link to…convenience vs control I guess.
    – If they are re-writing link URLs on your page on the fly I would also worry about unintentional side effects.

    I am a tech guy but don’t really do wordpress consulting. Usually doing consulting for companies around product strategy, competitor technical analysis or tech architecture. I’m only lightly into the WP topic because my wife started a blog.

    Good luck.

    Thread Starter mattpr

    (@mattpr)

    Hey Jacob, thanks for pointing me in that direction. New to WP and so missing a fair bit of context and detail about everything going on in the community. Looks like gutenberg may also solve some of my other pain points that I was planning to write custom plugins to address. So that’s great. Looks like most of the WP5 release schedule is still TBD so maybe I’ll try gutenberg in plugin form and see how stable it is at this point. Thanks again.

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