fullworks

The redirect happens before the page is loaded on so it is not really a redirect in that sense. i.e. it will just happen not be a load / reload ( don’t forget the exit after wp_redirect – also i’d use wp_safe_redirect )

Thats the way I’d do it ( and do in a similar way my 404 redirect plugin for instance )

You can’t update the options table for site url and that will impact every one.

You cant filter options_siteurl or options_home as that will impact many things that you could not control and would be a mess.

The alternative is for you code the logic at theme level, for instance in the header where it displays the logo with a home link apply the cookie lookup and in the menu apply logic too – there is a plugin that allows using shortcodes in menu items so you could write a simple shortcode to check the cookie.

Alternatively, if you are so inclined, you could examine the cookie in htaccess
e.g.

RewriteEngine On
RewriteCond %{HTTP_COOKIE} !cookie_name=specific_value; [NC]
RewriteRule ...

It looks like you have legacy jQuery which stopped being supported in WP 5.5 and you are on WP 5.6

Install this fixer plugin by the WordPress team

https://www.ads-software.com/plugins/enable-jquery-migrate-helper/

and I expect all will work.

Hi are you comfortable coding?

If so

hook into ‘comment_post’
https://developer.www.ads-software.com/reference/hooks/comment_post/

get the number of comments
https://developer.www.ads-software.com/reference/functions/get_comments_number/

if exceeds count update the $post->comment_status to ‘closed’

I assume as you are in ‘Developing with WordPress’ you are happy to code.

Fist you will want a cron job, running say daily

see https://developer.www.ads-software.com/plugins/cron/

then in the job you will need to identify the posts that have become eligible for stickiness by comparing the post date. Then you will need to add to the list of sticky posts. The sticky posts are stored in an option ‘sticky_posts’.

see https://developer.www.ads-software.com/themes/functionality/sticky-posts/ to understand how sticky posts are handled

I haven’t had had reusable blocks fail on my localhost installs.

I would suggest put the localhost site in debug mode and also checking the console log for errors to help determine what is wrong with your localhost setup.

Debugging in WordPress

Using Your Browser to Diagnose JavaScript Errors

Yes it is possible / feasible.

Custom code of course.

Use the ‘init’ hook to set the cookie, if not set.

Use the ‘template-redirect’ hook to inspect the cookie if set and redirect if landing on ‘real’ home to ‘temporary home’

There are many ways to run a self hosted WordPress website on your desktop computer, but beware making it publicly available without a hosting account is difficult and generally not advisable.

These are some search terms to help you research
– Docker WordPress Quickstart
– MAMP WordPress
– XAMMP WordPress
– Local WordPress

Sorry for the late answer here for some reason I did not get notified, maybe it ended in up in spam, I do try and answer free questions faster than that.

The demo should be the default settings, perhaps you made a change?

I’ll add a screenshot of the setting to that demo page

https://fullworks.net/docs/quick-paypal-payments/demos-quick-paypal-payments/basic-payment-form/

Hi Larry,

You are totally correct on all counts. When WP_DEBUG is on the all Warnings & Notices are displayed.

Notices & Warning as you say are not a problem, they are precisely warning & notices and do not impact functionality.

This plugin was handed to over me around a year ago and at that point was not well maintained.

I have been gradually clearing up the notices & warning and will continue to do so over time.

Best regards,

Alan

Thank you for taking the time to give this feedback.

Hi,

Thank you for your question.

Can you explain further what you want to achieve?

Currently the plugin auto generates a random custom field that gets stored and also sent to PayPal and comes back with the IPN and used to match off the payment record, this is integral to the way the plugin works today reporting that a payment has been processes and marked as paid when IPN processing is turned on.

Now it seems to only pop up on my dashboard, and not on the site.

OK this is an indication that the error is occurring ‘asynchronously’ ( normally an ajax call )

As above, the correct way to investigate is to turn on debug logs and then try and get the error.

Note the debug log may be full or warning & notices – but they are non issues – they are as they say warnings & notices. What you are looking for is Fatal errors.

Once you found the fatal error the cause should be clear by the file names.

It is likely the issue is
1. a plugin
2. something that is displaying notices – maybe to the dashboard
3. something that is making a call to a third party and storing that in a transient as a cache ( hence the irregularity )

Likely suspects would be something like displaying an analytics count or similar

But don’t let that stop you going through the debug route.

Alan

Hi

I note you are effectively asking for hired help to fix the issue, this probably isn’t the right forum for that as support is provided by volunteers in the community.

There are many ‘freelancer’ type websites and ‘wordpress fixing’ services and a quick search you will be able to find paid help.

You can eliminate most issues by ensuring your plugins & theme are up to date.

The issues tend to come from
1. using very old plugins that are no longer supported – in this case ofen the best option is to work out away of not using that plugin
2. custom themes, if you theme has been built from scratch there is no real option but to resort to code

In terms of effort, most of the effort is identifying the issue, once identified the changes normally are trivial

Alan

Hi

Are you saying these errors are from Google Search Console?

If you look you will see these are all program files, Google has no interest in these and they would not help your rankings.

It looks like your server was not properly secured at one stage and so Google ‘accidentally’ indexed your program files, and now your server is secure Google is being blocked.

I think this is a non-issue.

None of the files are mentioned in you sitemaps, eventually Google will give up on the php file.

But it could be related to your subdomain it.num1.co.il which has directory listings visible to the internet e.g. wp-includes ideally the server should be set to noindex directories

Hi sorry you are having difficulty.

Did you have a look at the guide here first? https://www.ads-software.com/support/article/moving-wordpress/#changing-your-domain-name-and-urls

It is difficult without seeing, but it is possible you did not update the links to the images in the database by replacing the old domain with new correctly.