Forum Replies Created

Viewing 12 replies - 1 through 12 (of 12 total)
  • You’re right – they both had the same url sitename/hostname setup…

    Not sure how that happened – I think I created the master and the slave didn’t have an installed database…

    Oh well, yip, yip, will get it into production.

    I have systematically gone through the theme searching the code for href and link and wrapping anything that I think produces a url in esc_url() and a lot of things are fixed, but there are still some major ones.

    The recent posts widget doesnt work, nor does most of themeta` widget, but most importantly the actual posts come with headlines and ‘posted by’ linking back to the other site.

    I can now login on the site, but it returns me to the master site.

    So far I have not added any esc_url()‘s to the core wordpress code – but I can’t see how I can get the RSS stuff to work without doing that. Changing the core wordpress stuff gives me a bad updgrade path, or should I copy their widgets over to the theme (Meta2?) and fix them there?

    Mark

    I am trying to setup a work flow here and I think I might be misusing SitePush a bit.

    The original plan was to push from the current production sites to new dev sites to creaet them.

    These would then become pre-production masters and I would always push back from them to the production sites.

    I know the theme I am going to be using (or the one that my production systems are going to be based on) should I be looking to ‘fix’ the widgets in that theme (are widgets part of themes?) or ‘fix’ the widgets in all themes?

    Ok, made all the /wordpress-master and /wordpress stuff go away – just fixing the URL stuff now…

    Any help appreciated…

    OK, I created two vanilla sites:
    * one on domain localhost with a file root of /usr/share/wordpress
    * one on domain wordpress.dev with a file root or /usr/share/wordpress-master

    These are using the 2012 theme.

    The fixed site url option is checked

    I pushed everything. The following links didn’t rewrite:
    * the sitename which should have been a link to localhost/wordpress was to localhost/wordpress-master
    * the top navigation home and sample page links were to wordpress.dev/wordpress-master
    * leave a reply on the front page comment was to wordpress.dev/wordpress-master
    * the categorized tag link was to localhost/wordpress-master
    * recent posts links were to wordpress.dev/wordpress-master
    * recent comments links were to localhost/wordpress-master
    * archives was to localhost/wordpress-master
    * categories was to localhost/wordpress-master
    * login was to localhost/wordpress-master
    * rss was to wordpress.dev/wordpress-master

    There is obviously a task to get rid of the /wordpress and /wordpress-master from each of the sites as that will make a **lot** of the issues go away (it is what I do for production sites).

    Then I need to figure out how to fix up the widgets, I suppose. Any clues appreciated.

    I had the same problem with permissions – figuring out that rsync needs you to be the owner of the directory so ownersip of root.www-data on files has to be www-data.www-data.

    Also the actual permissions you need in Mysql caused me a lot of grief…

    Will have a go with looking at the log in page…

    I have this problem as well. In particular I have copied two production sites over to the new staging sites with a view to making changes/retheming them in staging and then switching to a traditional stage -> production flow.

    But when I try and log into the staging servers the login prompt takes me to the production log in. I manually entered the login url on the staging domain but that didn’t work either.

    Plugin Author Gordon Guthrie

    (@gordonguthrie)

    Absolutely

    What you want is a form of calculator. There is a calculator HOWTO on the plugin site:
    https://wordpress.vixo.com/building-a-calculator-or-quote-engine/

    When you build the calculator you can add a graph to it (just like in a spreadsheet).

    Have a go with the HOWTO and if you hit any problems get back to me.

    Plugin Author Gordon Guthrie

    (@gordonguthrie)

    Fixed the activation bugs and pushed a new version of the plugin – it was a simple whitespace problem that I should have picked up on.

    You say you are getting server errors on the examples. Can you give me some more details? Are theyL
    * Vixo server errors
    * WordPress server errors
    * page not found notices
    * etc, etc

    Plugin Author Gordon Guthrie

    (@gordonguthrie)

    Apologies for taking so long to reply – I was under the impression that I was getting automatic notification of posts to this forum – but it turns out I wasn’t

    Yes, our plugin can do this. Ping me direct at gordon @ vixo dot com and I can show you how.

    The message is the problem…

    The real problem is that the field to put the link to the zip file of your plugin into can only take 80 chars.

    If your link is longer it fails and then gives you this not-so-helpful message…

    (I had to read the html of the submission page to start to work this out)

    I am getting this as well.

    I am trying to use the name vixo-wordpress but when I do I get this message.

    I search for a plugin of that name and it doesn’t work.

    I did try and create the plugin in subversion on my local machine before submitting this for – that also failed

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