ZainB

Hi Rachel,

Thanks for the Development version. I’ve been doing some testing and it seems to be working properly now.

Here’s what I’ve checked and found working:

• Show Admin radio buttons.
  Note: label also shows if ‘no’ Column title is provided.
• “Admin Column Title” appears correctly when text added.
• Metabox Format now work for all 3 – dropdown, checkbox and auto-complete
• Metabox Title text is saved properly.
• Has Archive Page radio buttons are saved.
• Archived Page Slug text is saved.

Admittedly, I’ve not checked the functionality of “Has Archived Page” and whether these work properly. Setting up additonal redirects is out of the remit of this issue.

Thanks for the quick reply and fix! It’s really appreciated. ??

Cheers,

Zain

Saying that… it doesn’t stick if you set it to “False”. And it does if you set it to “True”… weird.. ??

Actually, Has Archive Page does work. The values stay when the properties page is saved. My mistake…

Hi Evan,

Thanks again for your prompt reply. It’s good to know you take pride in your work, and that’s very re-assuring in terms of knowing how well this plugin is supported.

I’ve actually managed to fix the issue now. You’re right in saying it should work since both versions of CMB used are the same. So the issue was happening when the filter was being fired. By changing when the filters happen, I’ve found that the problem can be resolved.

For other users who may experience the same issue, here’s how I fixed it. I simply changed the filter function in my theme from:

add_filter( 'cmb_meta_boxes', 'my_metaboxes_name' );

to:

add_filter( 'init', 'be_sample_metaboxes' );

What this does is to fire the filter earlier, so by the time the Timeline Express plugin (or any other using the Custom Metaboxes and Fields for WordPress scripts) is called, there’s no clash. I think the problem is that WordPress gets confused when the same thing is fired at the same time.

I’m assuming this would be okay, unless someone else calls the filter upon init as well!

Anyway, thanks again for the support. And keep up the great work. Timeline Express is a great plugin and I’m looking forward to using it on my site now! ??

Cheers,

Zain

Hi Evan,

And WOW… thank you for your very prompt reply! I really appreciate it.

The Custom Metaboxes and Fields for WordPress version 1.2.0 (latest available from GitHub).

Any ideas how to get both working?

Cheers,

Zain

Hi Carrie,

If you hover over a link, you should be able to see “Edit | Delete | Disable”.

Click on Edit. Wait for the redirection to load.

On the far right of the Source URL field is the RegEx checkbox.

Either check or uncheck the box as necessary.

Unfortunately, there’s no bulk editing feature, so you may have to do these manually.

Good luck! ??

UPDATE:

I’ve just realised that using the “Source URL” above will mean that it may not be possible to access the Admin area.

It’s probably best to use:

Source URL: /(?!wp)(.*)
Target URL: https://www.newsite.com/$1

This will ensure that the /wp-xxxx/ folders and also wp-login.php remains untouched, and you can still log in.

Hope that helps.

@tom

Sometimes people don’t have access to FTP and can only add plugins (e.g. clients).

Adding a few lines of code is useful if you can get to your .htaccess file (and are comfortable with editing it without messing up WordPress).

Hi,

I’ve found you can redirect and old domain to a new one using RegEx, and have all old pages point to the same path on a new domain.

I’m currently using the following:

Source URL: /(.*)
Target URL: https://www.newsite.com/$1

IMPORTANT: Make sure you have the “regex” checkbox checked when saving your redirection.

If your site has previously been in Google, then you can check that the 301 redirections are working by doing a search for: “site:olddomain.com”. This will pull back all the URLs Google has stored for the site and clicking the links should redirect you to the new domain equivalent.

I hope this helps someone.

Cheers,

Zain

Hi s.r.

I’m not a regex wiz (I just know a little bit). Here’s what I came up with which seems to work. I hope it may help someone out (or even me in future!).

*Note: Remember to make sure that the Regex checkbox is ticked.

Source:
/post.php\?lg=eng&id=(\d+)

Target:
/courses/

Note the use of the parentheses (\d+). The \? helps to escape the question mark, as it’s a special character.

This will replace:

/post.php?lg=eng&id=35
/post.php?lg=eng&id=36
/post.php?lg=eng&id=45

and point them ALL to the /courses/ page.

===============
Alternate Useful Regex
How to redirect your URLs to a string, followed by an ID.

Source:
/post.php\?lg=eng&id=[\d+]

(Note the use of the brackets at the end [\d+] )

Target:
/courses/

This will replace:

/post.php?lg=eng&id=35
/post.php?lg=eng&id=36
/post.php?lg=eng&id=45

and point them to:
/courses/35/
/courses/36/
/courses/45/

I hope that helps. If anyone else can add anything, or suggest a better way, that would be great.

Cheers,

Zain

Hi s.r.,

Not sure if this helps, but here’s the Redirection plugin documentation page with a few examples:

https://urbangiraffe.com/plugins/redirection/

If you do find the solution, please could you post it? I’m going to have a play when I have a bit of time. I’m sure it would be useful.

Cheers,

Zain

Hi Mif,

One thing I forgot to mention – the Redirection plugin may store your original value (“/wp/*”) in the database, so the issue may appear again once you re-activate the plugin.

You might need to delete the (*prefix*)_redirection table from your database – depending on if you find the issue is happening again.

Good luck with it.

Cheers, Zain

Hi margje,

Sorry for the late reply. I’m not sure why there’s an issue. Off the top of my head, I’d be curious as to why the admin-ajax file is being called 3 times every minute. That’s a lot of calls to that page… The Redirection 404 script will log that file (which is why it’s probably appearing in your list). At a guess, I think another plugin could be triggering it… the problem is, identifying which one. The only way to find out is to disable all, then test each one to find the culprit.

Anyway, I just found out that John has recently updated the plugin (to 2.3.7). It’s not in the WP Repository, so you’ll need to download it from his site. I’ve posted the link in this thread:

https://www.ads-software.com/support/topic/redirection-v237-available-non-wp-repository-site-address?replies=1

It seems 2.3.6 had a few issues.

Good luck with your logs.

Zain

Hi creativeph,

This sounds like an interesting issue – I’ve got quite a few redirects set up and wondered if you can give me an example of a Google search where this is happening?

Just want to make sure it’s not happening on my sites too!

Cheers,

Zain

Hi Mimma,

That does sound like a major issue. How did you set up your redirects?

I’ve just answered a similar question in this thread:
https://www.ads-software.com/support/topic/where-does-the-plugin-store-the-redirects-need-to-fix-one-with-ftp?replies=3

In order to fix your issue, try using FTP then moving the Redirection plugin folder. You can find it here:

/wp-content/plugins/redirection/

Just move it to another location, then it can’t run. You should be able to log in again.

The problem you may have afterwards will be that the redirections that are set up will come back once you’ve re-activated the plulgin. You may need to remove the *_redirection tables from your database, so that the redirections are new.

Good luck with getting your site back.

Cheers,

Zain