Forum Replies Created

Viewing 15 replies - 16 through 30 (of 41 total)
  • Thread Starter Justin Handley

    (@justinhandley)

    I have checked and even changed the format in the google doc of those columns, but it hasn’t made a difference.

    Thread Starter Justin Handley

    (@justinhandley)

    It is member’s only content that we are loading – it is pulling stock market recommendations from a spreadsheet of stocks. I would be happy to send you only a member’s login. Or, I’ll make a temporary page..

    https://leibovitvrnewsletters.com/products/vr-trader-platinum/vr-platinum-portfolio-2/

    There you are – as you can see, the current price and profit / loss aren’t showing (should be number fields) and the Stop Loss only shows numbers, but not text values.

    Thread Starter Justin Handley

    (@justinhandley)

    To be honest, I disabled a plugin called nginx-helper and the errors disappeared. I also may have had some permission issues on the server – if your plugin tries to write to a directory it might not have been working. So far I don’t see any more errrors. I will write via email if it recurs.

    Thread Starter Justin Handley

    (@justinhandley)

    You are a genius! I didn’t even think of that. Yes – I set up a new spreadsheet in Google, added the Google Query to sort by date. Then, I was able to use my exact same shortcode against the new sheet. Thank you so much!

    Thread Starter Justin Handley

    (@justinhandley)

    Is there any chance you could take a look at what I posted here: https://webapps.stackexchange.com/questions/76218/google-query-for-dates-in-last-30-days

    It details the versions I’ve tried – I can’t get this to work for anything!

    I am running into something similar, and I wonder if it is related. I actually ran a test as a logged in admin and it pushed to Infusionsoft. But, when I ran the same test as a normal user it didn’t.

    This has been working fine. Has something changed?

    Yes, it works great. I use it on a ton of sites – fantastic for a free plugin.

    Thread Starter Justin Handley

    (@justinhandley)

    Hey John – sorry – so it isn’t quite resolved. That fixed it for some sites, but others still aren’t working. I have had other troubles, mostly related with migrating sites between two different multisite networks. Some issues with domain replacement, and some with errors like the fact that I renamed the database pre- extension, so what used to be wp_28_user_roles is at web_43_user_roles.

    Does your plugin check tables at all? Is it possible there is a migration error I haven’t uncovered that would only affect some sites? The error I’m getting is different now – I’m getting a 502…

    Thread Starter Justin Handley

    (@justinhandley)

    In fact, that is what it was. It was causing issues with this. It was causing issues with previewing posts. I guess it was a bad idea on my part. Once I mapped everything to the mapped domain it worked fine – probably related to cookies being written on one, and then trying to read them from the other.

    Thread Starter Justin Handley

    (@justinhandley)

    So here is my domain mapping. I am using nginx for the server, so the htaccess of the network setup doesn’t really apply anyway. One thing I noticed about other posts regarding this plugin was if the site url’s didn’t match exactly… would it make a difference if the admin url and front end url aren’t the same? Live sites are like yoursite.com. You log in at yoursite.com/wp-admin. But then you end up at yoursite.mysite.com/wp-admin once you are logged in. I do this so I can have better control of the dashboard experience. I could switch it so that it was yoursite.com/wp-admin, though, if that would make a difference.

    Administration mapping

    You can allow your members to access the administration area of your site through the domain they enter, you can also restrict it to the Mapped domain or the original domain (your website url):

    original domain

    Login mapping

    How should your members access the login page of their website, this can be through the domain they enter, or restrict it to either the Mapped domain or the original domain (your website url):

    mapped domain

    Cross-domain autologin

    Would you like for your members to be logged into all sites within your network regardless of domain name:

    No

    Verify domain’s DNS settings

    Would you like to verify domain’s DNS settings before they will be mapped by your members:

    No

    Force http/https (Only for original domain)
    Would you like to force https in login and admin pages:

    No

    Would you like to force http/https in front-end pages:
    No

    Thread Starter Justin Handley

    (@justinhandley)

    I can’t remember how I did his – it was a while ago, but you can always delete roles manually..

    function sf_remove_role() {
        remove_role( 'author' );
    }
    add_action( 'init', 'sf_remove_role' );

    Have you messed around with your theme?

    This line is coming from

    <aside class="post-meta">
    			...
    		</aside>

    Although I didn’t go too deep in the code, it looks like a failed attempt to float the post-meta box. I tried setting a couple of things to solve it and was unable to, so just hid it.

    You could do

    .post-meta {display:none;}

    in your CSS as a quick fix, or…

    1. If you’ve edited your theme, see if you’ve done anything to CSS / etc that would kill this.

    2. See if your theme has options – maybe there is a post-meta in your theme options that if you change the settings it will resolve this?

    Let me know if you get it.

    Hi David – it sounds like you are still caching somewhere. Who is your host? Is it possible that there is caching enabled at the server level? Are you using any other plugins that might cache like Cloudflare or Sucuri or Wordfence?

    Have you tried disabling all plugins?

    Also, what kind of updates don’t show up? Are you updating your theme / code, or is it actually edits to pages using the WordPress editor?

    Thread Starter Justin Handley

    (@justinhandley)

    This was caused by a hack. While I don’t have a list of all files cleaned, and really either your host or a security specialist should clean up (or better yet, you should restore your site to a previously working state), in the end what was causing the admin issue was base64 code inserted into the themes and plugins. It is at the very top of the file, and is a huge chunk of letters. In my case it was in every index.php, functions.php, and header.php file in my themes and plugins folder.

    Assuming all other security threats are cleaned, removing this will fix the admin issues. Or a clean reinstall of WordPress and your plugins and themes if you don’t have a backup.

    And, to be more specific – if you are still having this, take a look at the index, functions, and header files of your theme. They probably have big blocks of gibberish at the top. Delete those. Same with index files of plugins. That is what messes up the admin. However, just deleting them may not get rid of the malware – secure your stuff!

Viewing 15 replies - 16 through 30 (of 41 total)