Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
prev_next
Manage
Activity
Members
Labels
Plan
Wiki
Custom issue tracker
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Model registry
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
project
prev_next
Commits
360f447c
Commit
360f447c
authored
2 years ago
by
nita pawar
Committed by
Joao Ventura
2 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Issue
#3321893
by nitapawar, Nila Hyalij, jcnventura: Replace README.txt with README.md
parent
1a1a3e5a
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
README.md
+49
-0
49 additions, 0 deletions
README.md
README.txt
+0
-68
0 additions, 68 deletions
README.txt
with
49 additions
and
68 deletions
README.md
0 → 100644
+
49
−
0
View file @
360f447c
# PREVIOUS/NEXT API
## CONTENTS OF THIS FILE
-
Introduction
-
Requirements
-
Installation
-
Configuration
## INTRODUCTION
This module allows you to know the previous or next nodes for any given node.
This is very useful for providing navigational links to the user without the
expensive queries required to dynamically deduce such information on the fly.
-
For a full description of the module, visit the project page:
<https://www.drupal.org/project/prev_next>
-
To submit bug reports and feature suggestions, or to track changes:
<https://www.drupal.org/project/issues/prev_next>
## REQUIREMENTS
This module requires the following modules:
-
Block (Core)
## INSTALLATION
-
Install as you would normally [install a contributed Drupal module]
(https://www.drupal.org/docs/extending-drupal/installing-modules).
## CONFIGURATION
-
Configure prev/next settings at /admin/config/system/prev-next.
## INSTRUCTIONS
-
Add the Prev/Next block the a region.
-
Ensure the proper configuration is set admin/config/system/prev-next
-
Creating new nodes will auto-index and generate the Prev and Next links.
-
If there were already nodes created see below for indexing instructions.
-
For previously created nodes you will need to bulk save them. Go to your
content page and under bulk actions select 'Save Content" on all nodes that
you want to be indexes.
This diff is collapsed.
Click to expand it.
README.txt
deleted
100644 → 0
+
0
−
68
View file @
1a1a3e5a
CONTENTS OF THIS FILE
---------------------
* Introduction
* Requirements
* Installation
* Configuration
* Maintainers
INTRODUCTION
------------
This module allows you to know the previous or next nodes for any given node.
This is very useful for providing navigational links to the user without the
expensive queries required to dynamically deduce such information on the fly.
* For a full description of the module, visit the project page:
https://www.drupal.org/project/prev_next
* To submit bug reports and feature suggestions, or to track changes:
https://www.drupal.org/project/issues/prev_next
REQUIREMENTS
------------
This module requires the following modules:
* Block (Core)
INSTALLATION
------------
* Install as you would normally install a contributed Drupal module. See:
https://www.drupal.org/docs/8/extending-drupal-8/installing-contributed-modules-find-import-enable-configure-drupal-8
CONFIGURATION
-------------
* Configure prev/next settings at /admin/config/system/prev-next.
INSTRUCTIONS
------------
* Add the Prev/Next block the a region.
* Ensure the proper configuration is set admin/config/system/prev-next
* Creating new nodes will auto-index and generate the Prev and Next links.
* If there were already nodes created see below for indexing instructions.
* For previously created nodes you will need to bulk save them. Go to your
content page and under bulk actions select 'Save Content" on all nodes that
you want to be indexes.
MAINTAINERS
-----------
Current maintainers:
* Naveen Valecha - https://www.drupal.org/u/naveenvalecha
* Ben Hosmer - https://www.drupal.org/u/bhosmer
* Alex Ku - https://www.drupal.org/u/alexku
* João Ventura - https://www.drupal.org/u/jcnventura
* Khalid Baheyeldin - https://www.drupal.org/u/kbahey
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment