Archived topic

Why are there references to https://gpsites.co in the post GUID?

14 replies · Started by Former User on August 24, 2019

Viewing posts 1–15 of 15

August 24, 2019 at 7:40 pm #992625

Why do the themes include a GUID when posts are created e.g. https://gpsites.co/sider/?page_id=66?

August 25, 2019 at 9:13 am #993056

Hi there,

Those GUIDs are likely leftover from the import process when you import a post from gpsites.co (our Site Library). They shouldn't exist when you create a new post.

I'll see if there's a way we can update them during the import process :)

August 25, 2019 at 11:43 am #993160

Thanks Tom. Do the GUIDs have any dependencies? If no, can these be set to null or an empty string e.g ""?

August 25, 2019 at 4:13 pm #993335

This is a good article: https://deliciousbrains.com/wordpress-post-guids-sometimes-update/

It looks like something we need to address in the importer itself. If you're comfortable with databases, you can replace them: https://wordpress.stackexchange.com/questions/211156/how-to-change-all-the-guid-in-posts-table

August 25, 2019 at 7:10 pm #993392

Thanks Tom. That would be valuable.

Will you be releasing this for both new and existing sites? When would an update be available?

Based on the linked article, it appears that the GUIDs predominantly affect RSS feeds.

I have also observed that the URIs have the construct https://gpsites.co/sider/generatepress/. What is this URI intended for and what are it dependencies?

August 26, 2019 at 8:47 am #993900

Once we make the change in the importer, it will affect any site that's imported from then on. We won't make changes to any current sites as they are.

Not sure where that URI is coming from - where are you seeing it, exactly?

August 27, 2019 at 11:04 am #994843

Thanks Tom. It would be valuable to consider the ability to support existing sites.

The URI appears to be associate with a CSS configuration. It's an entry in the post table.

Is this expected?

@media (min-width: 1000px) {
	body {
		padding: 0 50px 50px;
		margin-left: 300px;
	}

	.site-header {
		position: fixed;
		left: 0;
		top: 0;
		width: 300px;
		z-index: 300;
		height: 100%;
		overflow: auto;
		overflow-x: hidden;
		-webkit-backface-visibility: hidden;
		-webkit-overflow-scrolling: touch;
		transition: .1s ease;
	}
	
	.admin-bar .site-header {
		top: 32px;
	}
	
	.site-header .main-navigation li {
		float: none;
	}
}

.inside-header {
	display: flex;
  flex: 1;
  flex-direction: column;
  align-items: center;
}

.site-branding,
.site-logo {
	order: 1;
}

.header-widget {
	order: 3;
}

.nav-float-right .inside-header .main-navigation {
	order: 2;
	float: none;
	margin-top: 30px;
	margin-bottom: 50px;
}

.nav-float-right .header-widget {
	float: none;
	top: auto;
	max-width: 100%;
}

#menu-social-sider li {
	display: inline-block;
	margin: 0 10px;
}

.dropdown-click .site-header .main-navigation ul ul {
    position: relative;
}

a.button,
a.button:visited,
button,
input[type="submit"] {
	border-width: 1px;
	border-style: solid;
	border-color: inherit;
}

.mc4wp-form-fields input {
	margin-bottom: 10px;
	width: 100%;
	text-align: center;
}

.single .entry-header::after,
.page .entry-header::after{
    border-bottom: 1px solid #000;
    content: "";
    display: block;
    margin-bottom: 40px;
    padding-bottom: 40px;
    width: 2.5%;
}

.main-navigation.toggled .main-nav li {
	text-align: center !important;
}

::-webkit-input-placeholder { 	text-transform: uppercase;
	font-size: 14px;
}

::-moz-placeholder {
	text-transform: uppercase;
	font-size: 14px;
}

:-ms-input-placeholder {
	text-transform: uppercase;
	font-size: 14px;
}

:-moz-placeholder {
	text-transform: uppercase;
	font-size: 14px;
}

@media (max-width: 768px) {
	.separate-containers .site-main {
		margin-top: 20px;
		margin-bottom: 0;
	}
	
	.post {
		margin-bottom: 20px;
	}
	
	.inside-header {
		padding: 30px;
	}
	
	html:not(.mobile-menu-open) .header-widget {
		display: none;
	}
	
	.nav-float-right .inside-header .main-navigation {
		margin-top: 0;
	}
	
	.nav-float-right .inside-header .main-navigation:not(.toggled) {
		margin-bottom: 0;
	}
}

April 11, 2020 at 1:50 am #1234846

Hi Tom.

The GUID appears to present when importing the latest site library "Charge".

In running the query below;

SELECT * FROM{database_name}_postsWHERE ping_status="closed";

it returns the value "https://gpsites.co/boost/wp-content/uploads/sites/48/2019/07/pexels-photo-351448-min.jpeg" for instance.

Similar entries appear for "https://gpsites.co/boost/?p=50"

April 11, 2020 at 10:43 am #1235467

ping_status is strange - are all of the references ping related?

April 11, 2020 at 12:09 pm #1235546

Hi Tom,

Here's an extract of the results. The output isn't as well formatted as it could be. There doesn't appear to be an option to upload files such as CSV.

https://gpsites.co/boost/wp-content/uploads/sites/48/2019/07/pexels-photo-219998-min.jpeg	attachment
https://gpsites.co/boost/wp-content/uploads/sites/48/2019/07/sunrise-phu-quoc-island-ocean-min.jpg	attachment
https://gpsites.co/boost/wp-content/uploads/sites/48/2019/07/pexels-photo-351448-min.jpeg	attachment
https://gpsites.co/boost/wp-content/uploads/sites/48/2019/07/pexels-photo-258122-min.jpeg	attachment
https://gpsites.co/boost/wp-content/uploads/sites/48/2019/07/pexels-photo-412086-min.jpeg	attachment
https://gpsites.co/boost/wp-content/uploads/sites/48/2019/07/pexels-photo-1450353-min.jpeg	attachment
https://gpsites.co/boost/wp-content/uploads/sites/48/2019/07/pexels-photo-1519088-min.jpeg	attachment
https://gpsites.co/boost/wp-content/uploads/sites/48/2019/07/pexels-photo-1165981-1-min.jpeg	attachment
https://gpsites.co/boost/wp-content/uploads/sites/48/2019/07/pexels-photo-1126380-min.jpeg	attachment
https://gpsites.co/boost/?p=50	custom_css
https://gpsites.co/boost/?p=53	nav_menu_item
https://gpsites.co/boost/?p=54	nav_menu_item
https://gpsites.co/boost/?p=55	nav_menu_item
https://gpsites.co/boost/?p=56	nav_menu_item
https://gpsites.co/boost/?p=57	nav_menu_item
https://gpsites.co/boost/?p=58	nav_menu_item
https://gpsites.co/boost/?p=59	nav_menu_item
https://gpsites.co/boost/?post_type=gp_elements&p=63	gp_elements
https://gpsites.co/boost/?post_type=gp_elements&p=64	gp_elements
https://gpsites.co/boost/?p=8	post
https://gpsites.co/boost/?p=12	post
https://gpsites.co/boost/?p=15	post
https://gpsites.co/boost/?p=18	post
https://gpsites.co/boost/?p=20	post
https://gpsites.co/boost/?p=23	post
https://gpsites.co/boost/?p=28	post
https://gpsites.co/boost/?p=31	post
https://gpsites.co/boost/?p=34	post
https://gpsites.co/boost/?page_id=39	page
https://gpsites.co/boost/?page_id=40	page
https://gpsites.co/boost/?page_id=41	page
https://gpsites.co/boost/?page_id=42	page
https://gpsites.co/boost/?page_id=43	page
https://gpsites.co/boost/?p=60	nav_menu_item
https://gpsites.co/boost/?p=61	nav_menu_item
https://gpsites.co/boost/?p=62	nav_menu_item

April 11, 2020 at 4:37 pm #1235717

Interesting, thanks for the information! I'll dig into this :)

April 22, 2020 at 12:34 am #1248818

Hi Tom,

Will you be releasing an update for it or is the current solution to delete these via SQL?

April 22, 2020 at 9:41 am #1249559

We won't be executing any code in the plugin to delete something from your database - that's typically a bad idea.

You can delete them via SQL, or even update the URLs using a plugin like this: https://wordpress.org/plugins/velvet-blues-update-urls/

We'll try to make it so this doesn't happen, but having them in the first place isn't a massive issue in itself: https://wordpress.stackexchange.com/questions/90206/wp-posts-guid-update/90209#90209

April 22, 2020 at 12:05 pm #1249756

Thanks Tom. It would be great if the base import process addresses the issue. It would overcome the need to update the database directly.

Given the site isn't live, we'll change and/or remove the GUID.

April 22, 2020 at 4:03 pm #1250051

I agree, I'll see what I can do :)

This archived topic is closed to new replies.

Start building better websites today.