Forum Replies Created

Viewing 15 replies - 76 through 90 (of 121 total)
  • Thread Starter oriver

    (@oriver)

    Hi @sterndata

    Thank you, I’ve done a very strong scan and everything looks okay no hacking or viruses. Will make a backup then and remove the sess_files. Thank you

    Thread Starter oriver

    (@oriver)

    @hcabrera

    Thanks deleted it no problem, and your plugin still works perfectly, thank you.

    Thread Starter oriver

    (@oriver)

    Hi @hcabrera

    Oh that’s great, so I should be okay to delete it then?

    Thread Starter oriver

    (@oriver)

    @sterndata

    I did have Elegant Themes a while back, thanks, will get rid of this now then. Never heard of Theme Grill, and never used it – this is the one with unreadable index, so I have no idea what to do with it.

    Do you know anything about Migbin, RCMTEMPthumb and session files?

    Thank you

    Thread Starter oriver

    (@oriver)

    Hi @hcabrera

    Thank you for your help.

    No that wasn’t a typo. That’s a bit suspicious then, will take a backup and delete. Thank you again

    Thread Starter oriver

    (@oriver)

    Hi @nlpro

    Thank you for clarifying this, may I ask when you say “Usually the iTSec plugin will add a cron job (purge-log-entries) with a daily schedule that is responsible for maintaining the logs size” do you know how I may get this to work?

    Thank you

    Thread Starter oriver

    (@oriver)

    Hi @sterndata

    So in the last 24 hours my website has recorded 2021 IP hits from my IP and 652 from the host IP. Most of these are admin-Ajax requests, which appears to be due to Heartbeat API but we haven’t even launched yet and this already seems very high, is this normal? And should we disable it?

    Thanks

    Thread Starter oriver

    (@oriver)

    @sterndata

    My apologies I was unclear, I’m aware of phpmyadmin and then browsing within the database but it doesn’t give the sort of breakdown of rows etc which I was hoping for, in order to find where the biggest pull of resources was. Perhaps this is beyond my scope for now. Thank you for all your help.

    Thread Starter oriver

    (@oriver)

    Hi @sterndata

    The website has become very very slow. Which they said was due to high IP logins from myself which is exorbitantly beyond high, and from themselves which they said is due to “loosely configured scripts of plugins on the account” but you get a new person each time they reply, so I’m not getting anywhere in knowing what’s going on, and Ive spent four full days looking at this with no luck.

    Thread Starter oriver

    (@oriver)

    Hi @t-p

    Sadly I keep getting a different person and they don’t know after they said it.

    While I looked at my Raw access for IP, and just today it shows 413 from my IP address and 400+ from the host. But they don’t know what is going on. The raw access log shows things like:

    GET /wp-admin/ HTTP/2.0″
    GET / HTTP/2.0″ 200
    GET /wp-admin/ HTTP/2.0″ 302
    POST /wp-cron.php
    GET /wp-includes/js/dist/
    GET /wp-includes/js/hoverIntent
    POST /wp-admin/admin-ajax
    GET / HTTP/1.1″ 301

    Grateful for any help

    Thread Starter oriver

    (@oriver)

    @sterndata

    Thank you, I’ll convert them now. Do you know how I can see what’s in these individual databases such as the “options” to check if there’s remnants of plugins etc.

    Thread Starter oriver

    (@oriver)

    Hi @adamwood

    Thank you I had a look at the Health Check plugin, but it had some worrying reviews, which I felt outweighed the risk of using it:( And no image errors on wordpress plugins or themes, or other image heavy websites.

    However, I realised that could the fault like with the images ‘on hover – scale’? Would this potentially cause the image tearing?

    Also just realised I have a no right click set on images too:

    add_action('wp_footer', 'wpsf_disallow_right_click_images');
    function wpsf_disallow_right_click_images() {
    ?>
    <script>
    	const images = document.getElementsByTagName('img');
    	for(var i = 0; i < images.length; i++) {
    		images[i].addEventListener('contextmenu', event => event.preventDefault());
    	}
    </script>
    <?php
    }

    Thanks again for your help.

    • This reply was modified 3 years, 12 months ago by oriver.
    • This reply was modified 3 years, 12 months ago by oriver.
    Thread Starter oriver

    (@oriver)

    Hi @psykro

    Sorry for the very late reply, I didn’t see a notification of your reply. The code snippet used is: https://wordpress.org/plugins/code-snippets/

    I had found that the following amendment fixed the errors, while the code seemed to still work on the staging site with no duplicates (but a different story for the live site). Having said this the change to the session_start() is causing duplicates on both sites now.

    However, this code might be helpful to others in order to remove the critical PHP errors caused by session_start(), while most codes should still work:
    ‘session_start([
    ‘cookie_lifetime’ => 86400,
    ‘read_and_close’ => true,
    ]);’

    Thread Starter oriver

    (@oriver)

    I’m guessing you mean in respect to the error message saying there is a problem on line 10? If that’s what you mean I’m sorry, I struggling to see what is wrong with it which is why I posted the initial question, as it doesn’t flag any error message on the staging site, so I don’t see how to change it for the live site as I don’t know why its different.

    Thread Starter oriver

    (@oriver)

    Hi @sterndata

    Thank you for coming back to me, I’ve tried a few post plugins, tried infinite scroll plugins, and have tried addons – which I contacted their support about and they recognise its a bug in their system regarding duplicates but its been 6 months and no fix. I’ve additionally self-funded developers who have formed codes but then somewhere or another there is an error or duplication. The closest I’ve got is the code in this post,(the one starting session_start) which works, but only when opening a first browser window, which I accepted would be limited, but then it comes up with that error on the live site which I wasn’t expecting, especially as it worked on the staging site with no error.

    The reason I want random posts is so that everyone has a chance for their hardwork to be equally seen, regardless of publication date, menu order, title order etc which meant some people would miss out, as their post – showing what they can do might be at the bottom. I wanted to create a site with equal opportunities even in the displaying of posts, which I felt random would achieve.

    Also not using caching unless its automatic with the host server. The only other thing is to display all posts and then randomise but this creates a very slow load up time.

    Would welcome any suggestions, or why the first code has an error on the live and not the staging so I might try a temporary fix.

    Thank you for your time and help.

Viewing 15 replies - 76 through 90 (of 121 total)