rechazame

O.o

Update:

Use action ‘pre_user_login’.

Source:

https://wordpress.stackexchange.com/questions/95300/hook-before-inserting-user-into-database

Thanks a lot Mark.

Thanks Mark, so the permalink update actually rewrites several rules to the DB and not the .htaccess.

Where then can I find information about the actual DB updates being made?

anyone please?

Haha, thanks! Have a nice day ??

Then I guess I will get my answers from the database… Sounds right. Thanks for the advice cslosel ??

And about the reason, yes, it is a bit strange to get into these details like that but I am doing it bc I wanted a collision proof way of assigning unique meaningless slugs to all posts and all terms regardless of their type. For example, I thought about generating a hash from a post ID and use that hash as the post slug. This way the slug is unique as there are no other ID numbers the same as this.

However, in spite of all that research, I ended up using a random 15 digit numbers as slugs and regenerate them if slug exist validation fails ??

Btw, any feedback about the approaches mentioned is welcome.

I was actually interested in understanding the way an ID (not a slug) is given to a post or a taxonomy when they are created.

For example:

1. Create a post of type post. A post is created with an ID of 8.
2. Create a post of type page. A post is created with an ID of 9.
3. Create a tag. A tag is created with an ID of 32.
4. Create a category. A category is created with an ID of 33.
5. Create a post of type book (a custom post type). A post is created with an ID of 10.

There you can see how the ID given to all post types is incremented with each creation of a post regardless of its type. However, the incrementation does not affect the ID given to a newly created taxonomy.

My question was what content share the same ID pool in WordPress? I am looking for a more extensive information than the one I have after performing the test I gave example of.

Thank you ??

Ugh.. Meant Mika* in the first sentence. Sorry.

I think the solution you suggested could work only if I can somehow embed a filtered calendar from the calendar site to the other sites.

Still looking into that.

Wow.. You never cease to amaze Mike. I am looking into it right now and also will ask Tribe if they have some other rabbit to pull for this one.

Thank you Mika

OMG how did you get to that?? Awesome. Sounds like this is exactly what’s going on. Looking forward to 4.1 then.

Thank you Mika

I actually didn’t think about the effect it would have on SEO… ??

Each site represents a different music genre community. Place is a CPT created by an event plugin (tribe’s event calendar) that each site runs for its own dedicated events. Often, a dance club would have activities that are relevant for several genres and so it is right for it appear on every site. That is why I wanted to hook into post_save and duplicate the post to other sites.

After putting down the scenario, can you think of a better solution to the situation than the one I came with?

If not, putting the pain aside, how bad it would impact my SEO?

Thank you Mika

Thank you both. I’m sticking with multisite.

I only need that to happen with on custom post type. Sites are identical in structure, not in content (except for that specific post type).

I was thinking about making the main site, which is basically not in use, as the index, in a way that post will be created in all sites, including main, and that the main site post id number will be saved to all other posts as a custom field.

This way I can recall each post from each site in order to perform updates etc.

What do you think?