StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6117164
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-05-24T21:30:56.453
FavoriteCount
0
LastActivityDate
2011-05-25T19:32:41.913
LastEditDate
2017-05-23T10:34:33.783
LastEditorUserId
-1
OwnerUserId
760850
ParentId
6063911
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I finally figure out how do not have duplicate urls parsing. First of all in config.php remove the suffix, better never user it: $config['url_suffix'] = ''; Then in routes.php never use wildcards and always uses regular expression. I.e, if i use: $route['(:any)/(:num)'] = 'homepage/parser/$1/$2'; this will work for all the following urls: <pre><code>/a/10 /a/10/11 /a/10/11/12 </code></pre> and so on! Instead: <pre><code>$route['([\w_-]+)/(\d+)'] = 'homepage/parser/$1/$2'; </code></pre> this only work for <pre><code>/a/10 </code></pre> and: <pre><code>$route['([\w_-]+).html'] = 'homepage/parser/$1'; </code></pre> will only work if you URLs really end in .html Unlucky /a/10.html/ is still a duplicate, so, i need at least one .htaccess rule to remove trailing slashes from URLs I really need unique URLs so i think i'm dropping any future codeigniter development for this project where i've mixed url: 1) .html 2) directories 3) old dynamic urls Instead i figure out that for SEO purpouse probably is the best to: - only use pages without extensions - avoid any directories So if this is the case (another project of mine), i just use plain URLs in my code and regular expressions in routes.php. The only issues is the trailing slash duplicate problem but this can be avoided globally with this .htaccess from this other solution: <a href="https://stackoverflow.com/questions/4167539/remove-trailing-slash-using-htaccess-except-for-home-landing-page">Remove trailing slash using .htaccess except for home / landing page</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POcodeigniter, how to avoid duplicated content because of the routes incorrect configuration?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USAntonio
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POcodeigniter, how to avoid duplicated content because of the routes incorrect configuration?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.