Forum Replies Created

Viewing 15 replies - 1 through 15 (of 27 total)
  • Thread Starter Callum

    (@aic_technologies)

    @khungate, thanks for the quick reply. I am referring to past campaign conversion tracking. I’m perplexed at this point if this is the case, shouldn’t there be a warning that removing the plugin does this? Why wouldn’t the data be stored in Mailchimp, and why can’t it be recovered in some way.

    Removing a plugin from a staging site, shouldn’t just destroy all the campaign metrics for the live site surely.

    Thread Starter Callum

    (@aic_technologies)

    Hi @khungate, thank you for the reply.

    I completed another fresh install but the problem persists, and now the data related to the most recent post-issue campaign is gone too, so it just seems to be historical data that is impacted, future/new data is working fine.

    Callum

    (@aic_technologies)

    Glad its not just me. I first thought another plugin must have added the marketing tab in. It’s bizarre that they are not at least placing them all under one parent menu.

    Thread Starter Callum

    (@aic_technologies)

    Hi Con,

    Thanks for taking the time to reply to my review.

    The plugin I was adding from memory was the Square Payment Gateway Addon/Plugin, which is free, but I had to go through the Woocommerce site to do this. Where I already had an account, I didn’t remember my password, so I had to reset my password, once I had reset my password, I then had to convert/merge my account with a WordPress account, in order to just download a free plugin.

    Its tricky to articulate without investing a lot of time into this reply. But it all just seemed completely counter-intuitive and pointless to me, and to Automatic. Since I had to leave a WordPress site, log into a non-WordPress (Woocommerce account) only to have to log into a WordPress account, and then switch back to my independently hosted WordPress website. No one has any more money than at the start, and it turned a 20-second task into 10 minutes of pure frustration.

    • This reply was modified 6 years, 4 months ago by Callum.
    • This reply was modified 6 years, 4 months ago by Callum.
    • This reply was modified 6 years, 4 months ago by Callum.
    Thread Starter Callum

    (@aic_technologies)

    Hi Steve,

    That worked for me also.

    Thank you genuinely for you help, really appreciate it.

    – Callum.

    Thread Starter Callum

    (@aic_technologies)

    Hi Steve,

    The theme being used is called Trek by PixelGrapes, I originally had it on the original version from when the site was build a year or so ago – 1.9.9. But I updated it today to 2.1. It didn’t resolve the issue.

    The dev who cut support at some point the last couple of months was kind enough to share the last updated version below with me – the 2.1 I updated to.

    https://cloud.pixelgrapes.com/1i3A0K1h2G0V

    There doesn’t appear to be a changelog anywhere.

    Interestingly the blog posts display as intended when viewed from within WordPress’s live customize feature. Just not on the live site.

    Callum.

    Thread Starter Callum

    (@aic_technologies)

    Hi Steve,

    Tried switching the theme, not sure why I didn’t think of that. That fixed the issue.

    Any idea what the issue might be then? Heres a link to a post that displayed as intended when the theme was switched – https://goo.gl/rpjLUt

    Developer of the theme cut support for the theme. I’m thinking at this point that it must be a compatibility issue with a version update of WordPress?

    Appreciate you replying to my message btw.

    – Callum.

    Thread Starter Callum

    (@aic_technologies)

    No same site structure and URL.

    And yes you would not think that! I have never seen the theme designer’s approach before.

    Apparently the problem is caused by a completely unrelated issue, where the host provider has changed PHP versions from 5.3 to 5.5, and now I apparently am expected to fix the incompatibles ??

    I suspect its near pointless trying to get that kind of help on here givin it could be a big task not really in the realm of WordPress, so thank you so much for your help Catacaustic I really appreciate it.

    Thread Starter Callum

    (@aic_technologies)

    Its all style related minus the font and custom css. The other WordPress instance using the same user name works fine and has full access to both MySQLs.

    I cannot find any exact reference to any single DB that it might create but within MYSQL it looks like it has created “wp_dt-frontpages” “wp_dt-sidebars” “wp_dt-styles” and others like it.

    DT is short handed for the theme name.

    It looks like all the actual WordPress DBs are working fine.

    Thread Starter Callum

    (@aic_technologies)

    Looking at the database files its odd (at least to me) that the website/WordPress can get access to all the other ‘mysql stuff’ and is able to show posts, pages etc but not others, all of which seem to relate to the styling of the website.

    Thread Starter Callum

    (@aic_technologies)

    Thank you so much for that information.

    I have checked the config file and that all seems to be fine.

    This is the actual code it is referring to, which makes me think its something to do with some code somewhere referencing the ‘old’ datebase with a different cpanel username at its front.

    “//CHECK FUNCTION
    function check_db_existance($table) {
    global $wpdb;
    $tables = mysql_list_tables(DB_NAME);
    while (list ($temp) = mysql_fetch_array ($tables)) {
    if ($temp == $table) {
    return TRUE;
    }
    }
    return FALSE;

    }

    Thread Starter Callum

    (@aic_technologies)

    hmmm my lazyness may have made me miss the closeness of the errors in terms of only 2 lines on the 1 file.

    Thread Starter Callum

    (@aic_technologies)

    Removed everything from the htaccess except the bit below. fixed the issue.

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    # END WordPress

    Thread Starter Callum

    (@aic_technologies)

    Removin the htaccess file has ruined the permilink structure… so I still need help ??

    Thread Starter Callum

    (@aic_technologies)

    Fixed the issue. For people that might have the same issue in the future if your error log (found through cpanel) looks the same try deleting the htaccess file that is bunched in with your WordPress install files (make a backup of coarse). In my case, it didnt need to be there and was causing the issue.

Viewing 15 replies - 1 through 15 (of 27 total)