അഭിപ്രായവേദി - സമീപകാല മാറ്റങ്ങൾ [ml]

ഫലകം:AuthorProfile/styles.css

VijayanPN — Wed, 12 Aug 2026 11:50:00 GMT

ഫലകം:AuthorProfile/styles.css താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

.author-profile-main {
display: flex;
gap: 20px;
align-items: flex-start;

max-width: 700px;
margin: 0 auto 20px;

padding: 20px;
border: 1px solid #ddd;
border-radius: 10px;
background: #fff;
box-shadow: 0 2px 5px rgba(0,0,0,.08);
}

.author-profile-photo {
flex: 0 0 200px;
}

.author-profile-photo img {
max-width: 200px;
height: auto;
border-radius: 6px;
}

.author-profile-bio {
flex: 1;
line-height: 1.7;
}

.author-profile-link {
margin-top: 15px;
font-weight: 600;
}

.author-profile-clear {
clear: both;
}

@media (max-width: 768px) {

.author-profile-main {
flex-direction: column;
}

.author-profile-photo {
text-align: center;
}

.author-profile-photo img {
max-width: 180px;
}
}
.author-articles-grid {
display: grid;
grid-template-columns: repeat(auto-fill, minmax(300px, 1fr));
gap: 20px;
margin-top: 20px;
}

ഫലകം:AuthorProfile

VijayanPN — Wed, 12 Aug 2026 11:46:09 GMT

ഫലകം:AuthorProfile താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

<includeonly><templatestyles src="Template:AuthorProfile/styles.css" /><div class="author-profile-main">{{#if: {{{AuthorPhoto|}}} | <div class="author-profile-photo">[[File:{{{AuthorPhoto|}}}|200px]]</div>
}}
<div class="author-profile-bio">{{{Bio|}}}</div>{{#if: {{{AuthorsiteLink|}}} |<div class="author-profile-link">
കൂടുതൽ വിവരങ്ങൾക്ക്:
[{{{AuthorsiteLink|}}} വെബ്സൈറ്റ് സന്ദർശിക്കുക]
</div>
}}
</div>
<h2>{{{Displayname|{{PAGENAME}}}}} എഴുതിയ ലേഖനങ്ങൾ</h2>
<div class="author-articles-grid">
{{#ask:
[[Author::{{FULLPAGENAME}}]]
|?#-=ArticlePage
|?Displayname=Displayname
|?Published date=Published date
|?Intro=Intro
|?Image1#200px=Image1
|format=template
|template=ArticleCard
|named args=yes
|limit=10
|sort=Published date
|order=descending
}}
</div>
<div class="author-profile-clear"></div>
<div style="display:none">
[[Displayname::{{{Displayname|{{PAGENAME}}}}}]]
{{#if:{{{AuthorPhoto|}}}|
[[AuthorPhoto::File:{{{AuthorPhoto}}}]]
}}
[[AuthorBio::{{{Bio|}}}]]
{{#if: {{{AuthorsiteLink|}}} |
[[AuthorsiteLink::{{{AuthorsiteLink|}}}]]
}}
[[Category:Authors]]
</div>
{{AuthorDirectoryLink}}
</includeonly>

ഫലകം:AuthorDirectoryLink

VijayanPN — Wed, 12 Aug 2026 11:40:40 GMT

ഫലകം:AuthorDirectoryLink താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

<templatestyles src="Template:AuthorDirectoryLink/styles.css" />
<div class="author-directory-link"><div class="author-directory-text">അഭിപ്രായവേദിയിലെ മറ്റ് ലേഖകരെ പരിചയപ്പെടുക</div><div class="author-directory-button">[[:Category:Authors|→ എല്ലാ ലേഖകരും]]</div>
</div>

ഫലകം:AuthorDirectoryLink/styles.css

VijayanPN — Wed, 12 Aug 2026 11:39:39 GMT

ഫലകം:AuthorDirectoryLink/styles.css താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

.author-directory-link {
margin-top: 2rem;
padding: 1rem 1.5rem;

border-top: 2px solid #d8e4f3;

text-align: center;

background: #f8fbff;
}

.author-directory-text {
font-size: 1rem;
margin-bottom: .5rem;
color: #444;
}

.author-directory-button a {
font-weight: 600;
text-decoration: none;
}

Private:Admins Priority List

VijayanPN — Tue, 11 Aug 2026 08:15:52 GMT

Private:Admins Priority List

VijayanPN — Tue, 11 Aug 2026 08:14:53 GMT

'= Phase 1 — Establish the new administrative foundation = Before touching the existing installation. === 1. Create the new Server Administrator account === * Create the account/user. * Assign the appropriate administrative group/rights. * Test login. * Verify that the administrator can perform the functions actually required. * Do not remove or reduce your own access yet. === 2. Establish administrative emai...' താൾ സൃഷ്ടിച്ചിരിക്കുന്നു

Draft:Documentation

VijayanPN — Tue, 11 Aug 2026 08:08:57 GMT

Knowledge Components

Draft:Documentation/Version 1.0/System Administration Manual/27 – Stewardship of Abhiprayavedi

VijayanPN — Mon, 10 Aug 2026 17:56:29 GMT

'{{DISPLAYTITLE:Chapter 27 – Stewardship of Abhiprayavedi}} {{DocumentationMetadata |manual=System Administrator's Manual |part=VI – Stewardship |chapter=27 |status=Draft }} {{DocumentationBreadcrumb |manual=System Administrator's Manual |part=VI – Stewardship |chapter=27 }} = Chapter 27 – Stewardship of Abhiprayavedi = The technical operation of Abhiprayavedi is only one part of its long-term survival. A p...' താൾ സൃഷ്ടിച്ചിരിക്കുന്നു

Draft:Documentation/Version 1.0/System Administration Manual

VijayanPN — Mon, 10 Aug 2026 17:55:47 GMT

Part VI — Stewardship

Draft:Documentation/Version 1.0/System Administration Manual/26– Disaster Recovery

VijayanPN — Mon, 10 Aug 2026 17:53:36 GMT

Draft:Documentation/Version 1.0/System Administration Manual/26– Disaster Recovery എന്ന താൾ Chapter 26 – Disaster Recovery എന്ന തലക്കെട്ടിലേയ്ക്ക് തിരിച്ചുവിടലില്ലാതെ VijayanPN മാറ്റി

Draft:Documentation/Version 1.0/System Administration Manual

VijayanPN — Mon, 10 Aug 2026 17:52:47 GMT

26. Disaster Recovery

25 - Troubleshooting and Error Diagnosis

VijayanPN — Mon, 10 Aug 2026 17:46:13 GMT

25 - Troubleshooting and Error Diagnosis എന്ന താൾ Chapter 25 – Troubleshooting and Error Diagnosis എന്ന തലക്കെട്ടിലേയ്ക്ക് തിരിച്ചുവിടലില്ലാതെ VijayanPN മാറ്റി

പുതിയ താൾ

{{DISPLAYTITLE:Chapter 25 – Troubleshooting and Error Diagnosis}}
{{DocumentationMetadata
|manual=System Administrator's Manual
|part=V – Maintenance
|chapter=25
|status=Draft
}}
= Chapter 25 – Troubleshooting and Error Diagnosis =

A MediaWiki failure does not necessarily mean that the MediaWiki installation itself is damaged.

An apparent failure may originate in several different layers:

* the browser or its JavaScript environment;
* MediaWiki;
* a MediaWiki extension;
* PHP;
* the MySQL database;
* the Apache web server;
* the hosting account or server configuration;
* a missing, damaged or incorrectly modified file;
* a configuration change in LocalSettings.php or
* a temporary hosting or resource problem.

The administrator's first responsibility is therefore **diagnosis**.

The guiding principle for Abhiprayavedi is:

{{Warning|'''Diagnose before restoring.''' A backup restoration should normally be a last resort, after the cause of the failure has been identified or reasonable diagnostic steps have been exhausted.}}

== 25.1 The Diagnostic Principle ==

When the wiki develops an error, do not immediately restore files or the database.

First determine:

# '''What has failed?'''
# '''When did it begin?'''
# '''Is the failure affecting everyone or only one user, browser, page or function?'''
# '''Is the problem in the browser, MediaWiki, PHP, database or web server?'''
# '''What error message or log entry identifies the failure?'''
# '''What was changed immediately before the failure appeared?'''

The last question is particularly important after:

* editing LocalSettings.php|LocalSettings.php
* installing or updating an extension;
* upgrading MediaWiki;
* changing PHP versions or settings;
* modifying CSS or JavaScript;
* changing permissions;
* changing database settings; or
* modifying server configuration.

A recent change is often the most useful clue.

{{Figure
|number=25-1
|title=Troubleshooting Flowchart
|file=Figure-25.1 Troubleshooting Flowchart.png
}}
The flowchart is a practical guide rather than a rigid procedure.

== 25.2 First Determine the Scope of the Problem ==

Before using diagnostic tools, establish the extent of the failure.

=== 25.2.1 One page only ===

If only one page fails while other pages work normally, investigate:

* the page itself;
* templates used by the page;
* embedded files;
* parser functions;
* Lua modules, if applicable;
* recently changed content; and
* extension functionality used by that page.

This does not normally indicate a complete server failure.

=== 25.2.2 One function only ===

If reading works but editing, uploading, searching, logging in or another specific function fails, investigate the component associated with that function.

For example:

* editing problems may involve VisualEditor, PageForms or JavaScript;
* uploading problems may involve file permissions or upload configuration;
* login problems may involve sessions, cookies or authentication;
* database-related failures may affect several MediaWiki functions simultaneously.

=== 25.2.3 Entire wiki unavailable ===

If the main page and ordinary article pages fail, the investigation should move outward from MediaWiki towards PHP and the web server.

Typical possibilities include:

* PHP failure;
* syntax error in LocalSettings.php|LocalSettings.php
* incompatible extension;
* missing MediaWiki file;
* incorrect file permissions;
* database connection failure;
* web-server configuration problem; or
* hosting/server failure.

== 25.3 Browser Developer Tools: Useful but Limited ==

Modern browsers provide Developer Tools, particularly the '''Console''' and '''Network''' panels.

These are useful for diagnosing client-side problems.

For example, the browser Console may show:

<syntaxhighlight lang="text">
Failed to load resource: the server responded with a status of 404 (Not Found)
</syntaxhighlight>

This can identify a missing image, JavaScript, CSS or SVG resource.

The Network panel can also show:

* HTTP status codes;
* failed requests;
* requests that never completed;
* response information; and
* resources that could not be loaded.

However, browser diagnostics should not automatically be interpreted as evidence of a MediaWiki or server failure.

=== 25.3.1 Browser-specific errors ===

The same page can produce different Console messages in different browsers.

An error displayed by Chrome/Chromium may therefore not appear in exactly the same form in Microsoft Edge or another browser.

This is particularly relevant to JavaScript.

For example, the following command:

<syntaxhighlight lang="javascript">
console.log(mw.config.get('wgUserName'));
</syntaxhighlight>

depends on the MediaWiki JavaScript environment being available in the page.

If the browser reports:

<syntaxhighlight lang="text">
Uncaught ReferenceError: mw is not defined
</syntaxhighlight>

this does not by itself prove that MediaWiki is malfunctioning.

It may indicate that:

* the command was executed on a page where the MediaWiki JavaScript object was not available;
* a required script had not loaded;
* the page was not fully initialized; or
* a browser-side resource failed to load.

Therefore browser Console errors must be interpreted in context.

{{Note|'''Rule of thumb:''' Browser Developer Tools are primarily a diagnostic tool for the client side. They should be combined with server-side evidence before concluding that the server or MediaWiki installation is damaged.}}

== 25.4 cPanel Error Information ==

The shared hosting control panel provides several useful diagnostic facilities.

These should normally be checked before attempting recovery.

=== 25.4.1 Errors ===

The cPanel '''Errors''' utility displays recent web-server error messages.

It can reveal problems such as:

* missing files;
* directory access problems;
* Apache errors;
* PHP-related failures;
* incorrect paths; and
* other web-server-level conditions.

For example, an entry such as:

<syntaxhighlight lang="text">
Cannot serve directory ... No matching DirectoryIndex found
and server-generated directory index forbidden by Options directive
</syntaxhighlight>

identifies a web-server directory access problem rather than a MediaWiki page-content problem.

The administrator should record the complete error message and the time at which it occurred.

=== 25.4.2 Error Pages ===

The cPanel '''Error Pages''' utility provides information about HTTP error codes.

Common codes include:

{| class="wikitable"
! Code
! Meaning
! Typical significance
|-
| 400
| Bad Request
| The request could not be understood or processed.
|-
| 401
| Authorization Required
| Authentication is required.
|-
| 403
| Forbidden
| Access to the requested resource is denied.
|-
| 404
| Not Found
| The requested resource does not exist.
|-
| 500
| Internal Server Error
| The server encountered an unexpected condition.
|-
| 502
| Bad Gateway
| A gateway or proxy received an invalid response.
|-
| 503
| Service Unavailable
| The service is temporarily unavailable.
|-
| 504
| Gateway Timeout
| A gateway did not receive a timely response.
|}

The code alone does not identify the cause.

For example, a '''500 Internal Server Error''' may result from:

* PHP failure;
* syntax error;
* incompatible extension;
* incorrect server configuration;
* permission problem; or
* another server-side condition.

The administrator should therefore use the code as the starting point for diagnosis rather than as the diagnosis itself.

== 25.5 cPanel Error Monitoring ==

The hosting environment may also provide an error-monitoring facility that reports problems detected for the website.

Abhiprayavedi currently has access to a website-monitoring facility that can report categories such as:

* uptime;
* performance;
* search-engine optimisation;
* content;
* security; and
* technology.

Such monitoring can be useful as an early warning system.

However, monitoring should be regarded as an '''alerting mechanism''', not as a substitute for examining the actual server and MediaWiki error information.

If an alert is received, the administrator should:

# note the time of the alert;
# determine whether the site is currently accessible;
# check cPanel error information;
# check MediaWiki logs where relevant;
# identify any recent change; and
# only then decide whether corrective action is necessary.

== 25.6 MediaWiki Logs ==

MediaWiki provides several built-in logs and diagnostic facilities.

=== 25.6.1 Recent Changes ===

'''Special:RecentChanges''' is primarily an editorial monitoring tool.

It records recent changes to wiki content and can help identify:

* unexpected edits;
* recent page creation;
* recent uploads;
* changes immediately preceding a problem; and
* unusual editorial activity.

It is not, however, a replacement for server error logs.

=== 25.6.2 Main Public Logs ===

'''Special:Log''' provides access to MediaWiki's public logs.

Depending on configuration and permissions, these may include events relating to:

* page deletion;
* page moves;
* uploads;
* user rights;
* protection;
* account activity; and
* other administrative actions.

Logs are particularly useful when an error appears to have followed an administrative operation.

=== 25.6.3 When to compare logs with the failure ===

If a problem began at approximately 20:30, for example, examine:

* Recent Changes around 20:30;
* Main public logs around 20:30;
* server error information around 20:30; and
* any relevant monitoring alert around 20:30.

Matching timestamps can often establish the sequence of events.

== 25.7 MediaWiki Diagnostic Settings in LocalSettings.php ==

When ordinary error information does not reveal the cause, MediaWiki provides temporary diagnostic settings through LocalSettings.php|LocalSettings.php}}.

These settings are powerful and must be used carefully.

{{Warning|'''Never leave detailed debugging or PHP error display enabled on the public wiki after troubleshooting.''' Diagnostic output may reveal internal paths, configuration information or other private information.}}

=== 25.7.1 Displaying PHP errors ===

MediaWiki's debugging documentation provides the following temporary settings:

<syntaxhighlight lang="php">
error_reporting( -1 );
ini_set( 'display_errors', 1 );
</syntaxhighlight>

These should be placed near the beginning of LocalSettings.php|LocalSettings.php}} when needed for diagnosis.

They may cause PHP errors to be displayed directly in the browser.

This can be especially useful when the wiki produces:

* a blank page;
* an unexplained HTTP 500 error;
* a PHP fatal error; or
* another server-side failure for which the ordinary interface provides insufficient information.

MediaWiki notes that some fatal PHP errors may occur before these settings are executed. In such cases, the web-server error log is more useful. :contentReference[oaicite:0]{index=0}

=== 25.7.2 Displaying MediaWiki exception details ===

For a MediaWiki exception, the following setting can temporarily provide a detailed stack trace:

<syntaxhighlight lang="php">
$wgShowExceptionDetails = true;
</syntaxhighlight>

This is particularly useful when MediaWiki displays a generic fatal-exception message without enough information to identify the cause.

The setting should be removed or disabled immediately after diagnosis because the detailed trace may reveal private information. :contentReference[oaicite:1]{index=1}

=== 25.7.3 Diagnostic settings are temporary ===

The recommended procedure is:

# Make a backup copy of the current LocalSettings.php|LocalSettings.php}} before modifying it.
# Add only the diagnostic setting required.
# Reproduce the error.
# Record the complete error message.
# Identify the likely cause.
# Correct the underlying problem.
# Remove or disable the diagnostic setting.
# Test the site again.

Do not accumulate multiple experimental settings unnecessarily.

== 25.8 MediaWiki Debug Logging ==

MediaWiki also supports logging diagnostic information to a file through configuration such as LocalSettings.php|$wgDebugLogFile}}.

For example:

<syntaxhighlight lang="php">
$wgDebugLogFile = '/path/to/debug.log';
</syntaxhighlight>

The exact location must be chosen carefully.

The log file must:

* be writable by the web application;
* not be publicly accessible; and
* be monitored so that it does not grow without control.

MediaWiki explicitly warns that debug logs can contain private information and should not be publicly accessible. :contentReference[oaicite:2]{index=2}

For Abhiprayavedi, such logging should not be introduced merely as a routine measure. It should be considered when ordinary cPanel and MediaWiki diagnostics are insufficient and a specific diagnostic requirement has been identified.

== 25.9 Database Diagnosis ==

A MediaWiki installation depends on its MySQL database.

The cPanel '''MySQL® Databases''' utility provides:

* database listing;
* database checking;
* database repair;
* database and user association information.

The '''Check Database''' function can be used when database integrity is suspected.

A successful check of the Abhiprayavedi database provides useful evidence that the database tables are structurally healthy.

{{Note|'''Do not use database repair merely because a MediaWiki error has occurred.''' First establish evidence that the database itself is the source of the problem.}}

=== 25.9.1 phpMyAdmin ===

phpMyAdmin provides a more detailed view of the database.

It can be useful for:

* confirming that the database exists;
* confirming the database server version;
* checking the database character set and collation;
* examining tables when specifically required; and
* performing controlled database administration.

The Abhiprayavedi database uses UTF-8/Unicode settings appropriate for Malayalam content.

phpMyAdmin should not be used for routine editing of MediaWiki content.

{{Warning|'''Do not modify MediaWiki tables directly in phpMyAdmin unless there is a specific, understood administrative reason and the consequences are known.''' Normal MediaWiki operations should be performed through MediaWiki itself.}}

== 25.10 Identifying the Layer of Failure ==

A useful way to approach an error is to move through the system layer by layer.

{| class="wikitable"
! Observation
! First place to investigate
|-
| Only one browser shows the problem
| Browser Developer Tools
|-
| One page or feature fails
| MediaWiki page, template or extension
|-
| HTTP 404
| Requested resource/path
|-
| HTTP 403
| Permissions or access configuration
|-
| HTTP 500
| PHP, MediaWiki, extension or web-server error information
|-
| Database-related error
| cPanel database tools, phpMyAdmin and MediaWiki diagnostics
|-
| Entire website unavailable
| cPanel error information, PHP and web-server environment
|-
| Problem begins immediately after configuration change
| Review the change first
|-
| Problem begins immediately after upgrade
| Check MediaWiki, PHP and extension compatibility
|}

The purpose of this table is not to prescribe a single solution. It identifies the most useful starting point for investigation.

== 25.11 A Practical Diagnostic Sequence ==

When Abhiprayavedi develops an unexplained technical error, follow this sequence.

=== Step 1 – Confirm the symptom ===

Determine exactly what is failing.

Do not rely on a description such as "the website is broken."

Record:

* the affected URL;
* the operation being attempted;
* the browser;
* the visible error message;
* whether another page works; and
* whether another browser produces the same result.

=== Step 2 – Check whether the problem is browser-side ===

If the page loads but a particular function fails, inspect the browser Console and Network panels.

Look for:

* 404 responses;
* JavaScript exceptions;
* failed requests;
* missing resources; and
* repeated network failures.

Do not assume that every Console error is related to the visible problem.

=== Step 3 – Check cPanel Errors ===

If the problem appears server-side, examine the cPanel '''Errors''' facility.

Record the relevant message and timestamp.

=== Step 4 – Check MediaWiki logs ===

Examine:

* Recent Changes;
* Main public logs; and
* any relevant MediaWiki diagnostic information.

=== Step 5 – Check database condition when appropriate ===

If the evidence suggests a database problem, use the cPanel database '''Check''' function.

Use phpMyAdmin only when more detailed investigation is required.

=== Step 6 – Examine recent changes ===

Review anything changed immediately before the failure:

* LocalSettings.php|LocalSettings.php
* MediaWiki;
* extensions;
* PHP;
* templates;
* CSS;
* JavaScript;
* permissions; or
* server settings.

=== Step 7 – Enable temporary diagnostics if necessary ===

Only when the cause remains unclear should temporary PHP or MediaWiki diagnostic settings be introduced.

Record the exact error before changing anything further.

=== Step 8 – Correct the cause ===

Once the cause has been identified, correct that cause rather than restoring unrelated parts of the system.

=== Step 9 – Disable temporary diagnostics ===

Remove diagnostic settings such as:

<syntaxhighlight lang="php">
error_reporting( -1 );
ini_set( 'display_errors', 1 );
$wgShowExceptionDetails = true;
</syntaxhighlight>

unless there is a specific reason to retain them temporarily.

=== Step 10 – Test the complete site ===

After correction, test at least:

* main page;
* representative article;
* login;
* editorial access;
* editing;
* image display;
* search;
* relevant forms; and
* any function involved in the original failure.

Only after successful testing should the incident be considered resolved.

== 25.12 When Restoration Becomes Necessary ==

Restoration from backup is an important recovery capability, but it should normally be the '''last resort'''.

Restoration may become appropriate when:

* important files have been lost or corrupted;
* the database has suffered significant damage;
* a failed upgrade cannot be safely repaired;
* configuration damage cannot otherwise be corrected;
* the cause is known and the affected state must be rolled back; or
* other recovery methods have failed.

The administrator should first establish:

# what component is damaged;
# which backup contains the required healthy state;
# what information will be lost by restoration; and
# whether files and database must be restored together.

The backup and recovery procedures are described in [[Chapter 23 – Backup and Recovery]].

== 25.13 Keep an Incident Record ==

For a significant failure, record:

* date and time;
* symptom;
* affected functions;
* error message;
* relevant log entry;
* recent changes;
* diagnostic steps;
* identified cause;
* corrective action;
* whether backup restoration was required; and
* final test result.

This record becomes valuable when a similar failure occurs again.

It also prevents repeated investigation of the same problem without reference to the earlier solution.

== 25.14 Troubleshooting Philosophy for Abhiprayavedi ==

The administrator should adopt five habits:

# '''Observe before changing.'''
# '''Record the exact error.'''
# '''Identify the failing layer.'''
# '''Change one thing at a time.'''
# '''Restore only when diagnosis and repair are no longer practical.'''

The most dangerous troubleshooting practice is to make several changes at once and then lose the ability to determine which change solved—or caused—the problem.

For a long-lived publishing system, the ability to identify the cause is more valuable than the ability to restore blindly.

{{DocumentationBreadcrumb|manual=System Administrator's Manual|part=V – Maintenance}}

[[Category:Documentation]]

26 - 26 – Disaster Recovery

VijayanPN — Mon, 10 Aug 2026 17:42:38 GMT

26 - 26 – Disaster Recovery എന്ന താൾ Draft:Documentation/Version 1.0/System Administration Manual/26– Disaster Recovery എന്ന തലക്കെട്ടിലേയ്ക്ക് തിരിച്ചുവിടലില്ലാതെ VijayanPN മാറ്റി

പുതിയ താൾ

{{DISPLAYTITLE:Chapter 26 – Disaster Recovery}}
{{DocumentationBreadcrumb|manual=System Administrator's Manual|part=V – Maintenance|chapter=26}}
{{DocumentationMetadata|manual=System Administrator's Manual|part=V – Maintenance|chapter=26|status=Draft}}
= Chapter 26 – Disaster Recovery =
The purpose of disaster recovery is to restore Abhiprayavedi when ordinary troubleshooting and maintenance are no longer sufficient.

A disaster may involve:

* loss of access to the hosting account;
* serious corruption of the hosting environment;
* loss or corruption of MediaWiki files;
* loss or corruption of the MediaWiki database;
* accidental or incomplete restoration;
* failure of the hosting account requiring a replacement account.

The most important principle is:

'''Disaster recovery normally means restoring the existing Abhiprayavedi installation — not installing MediaWiki again from the beginning.'''

The existing installation, its uploaded files, configuration, extensions, customisations and database should therefore be preserved through reliable backups.
{{Figure
|number=26-1
|file=Figure-26-1-Restoration.svg | 900px
|title=Disaster Recovery and Restoration Path
|caption=The principal recovery paths for restoring Abhiprayavedi after a major failure.
}}
== 26.1 The Recovery Principle ==
Abhiprayavedi consists of two major categories of information that must be preserved:
{| class="wikitable"
!Component
!What it contains
!Principal recovery resource
|-
|MediaWiki files
|MediaWiki core, extensions, skins, images, configuration, custom CSS/JavaScript and other website files
|Home Directory / Full Account Backup
|-
|MediaWiki database
|Pages, revisions, users, permissions, categories, templates and other database content
|MySQL Database Backup / Full Account Backup
|}
A successful recovery therefore requires both the '''application files''' and the '''database'''.

Restoring only the files does not restore the content of the wiki.

Restoring only the database does not restore the complete MediaWiki installation.

== 26.2 First Question: Is the Hosting Account Still Available? ==
When a major failure occurs, the administrator should first determine whether the hosting account itself is still accessible.

=== 26.2.1 Hosting access problem ===
If the website is functioning but the administrator cannot log in to cPanel, this is primarily an '''account-access problem'''.

Examples include:

* forgotten or lost credentials;
* a locked hosting account;
* authentication problems;
* temporary hosting-provider restrictions.

In such cases, contact the hosting provider and restore administrative access.

'''Do not begin a MediaWiki reconstruction merely because cPanel access has been lost.'''

=== 26.2.2 Hosting account failure ===
If the hosting account itself has been lost, seriously corrupted, terminated, or otherwise cannot be recovered normally, contact the hosting provider.

The objective is either:

# restoration of the existing hosting account; or
# provision of a replacement hosting account.

If the provider can restore the account from its own infrastructure backups, this is generally preferable to rebuilding the site manually.

If a replacement hosting account is required, proceed with the backup-based recovery described below.

== 26.3 The Full Account Backup ==
The Full Account Backup is the principal comprehensive disaster-recovery resource.

{{Figure
|number=26-2
|file=Figure-26-2-Full-Account-Backup.png
|900px
|title=Full Account Backup
|caption=The cPanel Full Backup facility creates an archive of the hosting account's files and configuration. Full account backups are downloaded and preserved outside the hosting account for disaster recovery.
}}

The cPanel Backup facility describes a full backup as an archive containing the website's files and configuration. It is intended for keeping a copy of the account or moving the account to another server.

For Abhiprayavedi, the full backup is important because it preserves much more than the visible article content.

It may include:

* the MediaWiki core;
* installed extensions;
* skins;
* uploaded images;
* <code>LocalSettings.php</code>;
* custom CSS and JavaScript;
* other MediaWiki files;
* the home directory;
* MySQL databases;
* relevant hosting-account configuration.

The exact contents should be verified against the hosting provider's backup implementation.

=== Important limitation ===
A full cPanel account backup '''cannot normally be restored by the account holder through the ordinary cPanel interface'''.

The cPanel interface provides the facility to generate and download the full backup. Restoration of a full account backup may require the hosting provider or server administrator.

Therefore:

'''A full backup should be downloaded and preserved outside the hosting account.'''

A backup stored only inside the same hosting account is not sufficient protection against complete loss of that account.

== 26.4 Component-Level Recovery Resources ==
In addition to the full account backup, cPanel provides separate recovery resources.

{{Figure
|number=26-3
|file=Figure-26-3-Backup-Restore-Facilities.png
|900px
|title=Backup and Restore Facilities
|caption=cPanel provides separate facilities for downloading and restoring Home Directory and MySQL database backups.
}}
=== 26.4.1 Home Directory Backup ===
The Home Directory backup contains the website files stored within the hosting account.

{{Figure
|number=26-4
|file=Figure-26-4-MediaWiki-Files.png
|900px
|title=MediaWiki Files in the Hosting Account
|caption=The MediaWiki installation and its site-specific files are stored within the hosting account, including the public_html directory, extensions, images, skins, vendor files and configuration.
}}
For Abhiprayavedi, the MediaWiki installation is located within the site's <code>public_html</code> directory under the hosting account.

The relevant files include:

* MediaWiki core;
* <code>extensions/</code>;
* <code>skins/</code>;
* <code>images/</code>;
* <code>resources/</code>;
* <code>vendor/</code>;
* <code>LocalSettings.php</code>;
* custom CSS and JavaScript;
* other MediaWiki and site-specific files.

The exact directory structure should be confirmed against the current installation before a recovery operation.

=== 26.4.2 MySQL Database Backup ===
The MediaWiki database contains the actual wiki data.

It includes, among other things:

* article text;
* revision history;
* users;
* user groups and permissions;
* templates;
* categories;
* page properties;
* logs;
* other MediaWiki database information.

The current Abhiprayavedi database name is recorded in the System Administrator's configuration records.

The database backup should therefore be preserved separately from the website files.

=== 26.4.3 Why both are needed ===
A complete MediaWiki recovery requires both:

'''Website files + MediaWiki database'''

The Home Directory backup alone cannot recreate the database content.

The database backup alone cannot recreate the complete MediaWiki installation.

The Full Account Backup provides the broadest single recovery archive, while the separate Home Directory and MySQL backups provide useful component-level recovery options.

== 26.5 Normal Restoration Path ==
Where the hosting account or replacement account is available, recovery should proceed from the least disruptive method to the most extensive.

=== Step 1 – Establish hosting access ===
Confirm that the administrator can access the hosting control panel.

If necessary, obtain assistance from the hosting provider.

=== Step 2 – Determine what has been lost ===
Before restoring anything, establish whether the problem concerns:

* the hosting account;
* MediaWiki files;
* the database;
* both files and database;
* or only a particular component.

Do not overwrite functioning files or databases unnecessarily.

=== Step 3 – Preserve the current state ===
If the damaged installation is still accessible, preserve whatever remains before beginning restoration.

This may include:

* downloading the current Home Directory;
* downloading the current database;
* preserving <code>LocalSettings.php</code>;
* recording the current MediaWiki version;
* recording installed extensions and other important configuration.

This precaution may be valuable if the initial diagnosis proves incorrect.

=== Step 4 – Restore the required files ===
If MediaWiki files have been lost or corrupted, restore the Home Directory or the relevant files from the available backup.

Where the full account is being restored by the hosting provider, this step may be performed as part of the account restoration.

=== Step 5 – Restore the database ===
Restore the MediaWiki MySQL database from the appropriate database backup.

The database name, database user and permissions must correspond with the restored <code>LocalSettings.php</code> configuration or be adjusted appropriately.

=== Step 6 – Verify the installation ===
Do not consider the recovery complete immediately after the restoration process finishes.

The administrator must verify:

* the main page;
* representative articles;
* Malayalam and English content;
* article revision history;
* user login;
* editorial access;
* images;
* templates;
* categories;
* forms;
* custom CSS and JavaScript;
* important extensions;
* the Editorial Access workflow.

The site should be tested from both desktop and mobile browsers.

== 26.6 Recovery Does Not Normally Mean Reinstalling MediaWiki ==
This distinction is important for future administrators.

If the Home Directory has been successfully restored, the existing MediaWiki installation is already present.

There is normally no reason to:

* download MediaWiki again;
* reinstall every extension;
* recreate the directory structure;
* recreate the uploaded images;
* rebuild the custom CSS;
* recreate <code>LocalSettings.php</code>.

The administrator is restoring the existing installation.

Manual installation becomes necessary only when the original files cannot be recovered or when the existing installation is unusable.

== 26.7 Manual Reconstruction – Last Resort ==
If neither a usable Full Account Backup nor usable component backups are available, Abhiprayavedi may have to be reconstructed manually.

This is the most demanding recovery route.

The reconstruction would generally involve:

# obtaining the appropriate MediaWiki version;
# creating the required hosting directories;
# restoring or reinstalling the required extensions;
# restoring the uploaded images;
# restoring <code>LocalSettings.php</code>;
# restoring custom CSS and JavaScript;
# restoring other site-specific files;
# creating or configuring the MySQL database;
# importing the MediaWiki database dump;
# configuring the database connection;
# verifying file permissions;
# testing MediaWiki;
# testing the extensions and custom functionality;
# testing the editorial workflow.

The System Administrator's Manual, Release Reference Manual and other Abhiprayavedi documentation become especially important during this process.

'''Manual reconstruction should therefore be regarded as the last-resort recovery method, not the normal recovery procedure.'''

== 26.8 Verification After Recovery ==
A technically successful restoration is not necessarily a functionally successful restoration.

The administrator should carry out a structured verification.

=== Basic site test ===
Check:

* Main Page;
* representative Malayalam article;
* representative English article;
* article images;
* categories;
* search;
* navigation;
* mobile display.

=== Editorial test ===
Check:

* Editorial Access;
* administrator login;
* editor login;
* Create Article;
* Drafts;
* Submissions;
* Edit with Form;
* publication workflow.

=== System test ===
Check:

* MediaWiki version;
* installed extensions;
* <code>LocalSettings.php</code>;
* custom CSS;
* custom JavaScript;
* database connectivity;
* uploaded files;
* permissions.

=== Documentation test ===
Check that the System Administrator's Manual and other essential documentation remain available.

If documentation was stored only inside the damaged hosting account, retrieve the separately preserved documentation copy.

== 26.9 Recovery Records ==
Every major recovery should be documented.

Record:
{| class="wikitable"
!Item
!Record
|-
|Date and time
|When the recovery began and ended
|-
|Cause
|Known or suspected cause of the failure
|-
|Hosting status
|Existing account restored or replacement account used
|-
|Backup used
|Full Account, Home Directory, MySQL or other backup
|-
|Backup date
|Date of the backup used
|-
|Restoration actions
|Major steps performed
|-
|Problems encountered
|Errors or unexpected behaviour
|-
|Verification
|Tests performed after restoration
|-
|Final status
|Whether the site was fully restored
|}
These records provide valuable information for future administrators and may reveal weaknesses in the backup or recovery process.

== 26.10 Recovery Priorities ==
When a serious failure occurs, the administrator should avoid attempting to fix everything simultaneously.

The recommended priority is:

# '''Restore control of the hosting environment.'''
# '''Preserve any surviving data.'''
# '''Identify the extent of the failure.'''
# '''Select the appropriate backup.'''
# '''Restore the MediaWiki files.'''
# '''Restore the database.'''
# '''Verify MediaWiki itself.'''
# '''Verify the editorial system.'''
# '''Verify the reader interface.'''
# '''Record the recovery.'''

The objective is not merely to make the homepage appear again.

The objective is to restore a functioning Abhiprayavedi platform.

== 26.11 Backup Discipline and Disaster Readiness ==
Disaster recovery is effective only when usable backups exist before the disaster occurs.

The following principles therefore apply:

* Maintain periodic Full Account Backups.
* Download backups outside the hosting account.
* Maintain accessible copies of the Home Directory and MySQL backups.
* Preserve the current <code>LocalSettings.php</code>.
* Preserve important configuration information.
* Keep the System Administrator's Manual outside the live site as well.
* Record the MediaWiki version and installed extensions.
* Periodically verify that backup files can actually be accessed.
* Do not assume that the existence of a backup file guarantees a successful restoration.

The backup system should be regarded as part of the Abhiprayavedi infrastructure, not merely as an emergency convenience.

== 26.12 The Recovery Test Problem ==
A complete disaster-recovery exercise is difficult to perform on the live Abhiprayavedi site because an actual restoration can itself introduce risk.

A practical approach is therefore to maintain good documentation of the recovery procedure and, where possible, perform limited verification of individual recovery components.

For example:

* verify that a Full Account Backup can be downloaded;
* verify that a Home Directory backup can be downloaded;
* verify that a MySQL backup can be downloaded;
* verify that the backup files are readable and stored outside the hosting account;
* verify that the current MediaWiki version and configuration information are recorded.

A future administrator should not discover the location or nature of the backups for the first time during an actual disaster.

== 26.13 Recovery Completion Checklist ==
{| class="wikitable"
!Check
!Completed
|-
|Hosting access restored
|☐
|-
|Cause or extent of failure identified
|☐
|-
|Surviving data preserved
|☐
|-
|Appropriate backup selected
|☐
|-
|MediaWiki files restored
|☐
|-
|Database restored
|☐
|-
|<code>LocalSettings.php</code> verified
|☐
|-
|Extensions verified
|☐
|-
|Images verified
|☐
|-
|Templates and forms verified
|☐
|-
|Administrator login verified
|☐
|-
|Editorial workflow verified
|☐
|-
|Reader interface verified
|☐
|-
|Mobile interface verified
|☐
|-
|Recovery documented
|☐
|}

== 26.14 Final Principle ==
The long-term survival of Abhiprayavedi does not depend upon preventing every possible failure.

Failures will occur.

What matters is whether the platform can be understood, recovered and restored by someone other than the person who originally built it.

The combination of:

* documented architecture;
* reliable backups;
* preserved configuration;
* separate recovery resources;
* a documented restoration procedure; and
* post-recovery verification

turns a catastrophic failure into a recoverable administrative event.

'''The purpose of disaster recovery is not simply to save files. It is to preserve the ability to restore Abhiprayavedi as a functioning publishing platform.'''

Draft:Documentation/Version 1.0/System Administration Manual

VijayanPN — Mon, 10 Aug 2026 17:39:07 GMT

26 - 26 – Disaster Recovery

VijayanPN — Mon, 10 Aug 2026 16:43:31 GMT

26.4 Component-Level Recovery Resources

←പഴയ രൂപം		22:13, 10 ഓഗസ്റ്റ് 2026-നു നിലവിലുണ്ടായിരുന്ന രൂപം
വരി 126:		വരി 126:
	\|caption=cPanel provides separate facilities for downloading and restoring Home Directory and MySQL database backups.		\|caption=cPanel provides separate facilities for downloading and restoring Home Directory and MySQL database backups.
	}}		}}
			=== 26.4.1 Home Directory Backup ===
			The Home Directory backup contains the website files stored within the hosting account.

	{{Figure		{{Figure
വരി 134:		വരി 136:
	\|caption=The MediaWiki installation and its site-specific files are stored within the hosting account, including the public_html directory, extensions, images, skins, vendor files and configuration.		\|caption=The MediaWiki installation and its site-specific files are stored within the hosting account, including the public_html directory, extensions, images, skins, vendor files and configuration.
	}}		}}
	~~=== 26.4.1 Home Directory Backup ===~~
	~~The Home Directory backup contains the website files stored within the hosting account.~~

	For Abhiprayavedi, the MediaWiki installation is located within the site's <code>public_html</code> directory under the hosting account.		For Abhiprayavedi, the MediaWiki installation is located within the site's <code>public_html</code> directory under the hosting account.

പ്രമാണം:Figure-26-3-Backup-Restore-Facilities.png

VijayanPN — Mon, 10 Aug 2026 16:42:11 GMT

VijayanPN പ്രമാണം:Figure-26-3-Backup-Restore-Facilities.png അപ്‌ലോഡ് ചെയ്തു

പുതിയ താൾ

26 - 26 – Disaster Recovery

VijayanPN — Mon, 10 Aug 2026 16:41:38 GMT

26.4 Component-Level Recovery Resources

←പഴയ രൂപം		22:11, 10 ഓഗസ്റ്റ് 2026-നു നിലവിലുണ്ടായിരുന്ന രൂപം
വരി 118:		വരി 118:
	== 26.4 Component-Level Recovery Resources ==		== 26.4 Component-Level Recovery Resources ==
	In addition to the full account backup, cPanel provides separate recovery resources.		In addition to the full account backup, cPanel provides separate recovery resources.

			{{Figure
			\|number=26-3
			\|file=Figure-26-3-Backup-Restore-Facilities.png
			\|900px
			\|title=Backup and Restore Facilities
			\|caption=cPanel provides separate facilities for downloading and restoring Home Directory and MySQL database backups.
			}}

	{{Figure		{{Figure
	\|number=26-4		\|number=26-4

പ്രമാണം:Figure-26-4-MediaWiki-Files.png

VijayanPN — Mon, 10 Aug 2026 15:14:58 GMT

VijayanPN പ്രമാണം:Figure-26-4-MediaWiki-Files.png അപ്‌ലോഡ് ചെയ്തു

പുതിയ താൾ

26 - 26 – Disaster Recovery

VijayanPN — Mon, 10 Aug 2026 15:14:31 GMT

26.4 Component-Level Recovery Resources

←പഴയ രൂപം		20:44, 10 ഓഗസ്റ്റ് 2026-നു നിലവിലുണ്ടായിരുന്ന രൂപം
വരി 118:		വരി 118:
	== 26.4 Component-Level Recovery Resources ==		== 26.4 Component-Level Recovery Resources ==
	In addition to the full account backup, cPanel provides separate recovery resources.		In addition to the full account backup, cPanel provides separate recovery resources.
			{{Figure
			\|number=26-4
			\|file=Figure-26-4-MediaWiki-Files.png
			\|900px
			\|title=MediaWiki Files in the Hosting Account
			\|caption=The MediaWiki installation and its site-specific files are stored within the hosting account, including the public_html directory, extensions, images, skins, vendor files and configuration.
			}}
	=== 26.4.1 Home Directory Backup ===		=== 26.4.1 Home Directory Backup ===
	The Home Directory backup contains the website files stored within the hosting account.		The Home Directory backup contains the website files stored within the hosting account.

പ്രമാണം:Figure-26-2-Full-Account-Backup.png

VijayanPN — Mon, 10 Aug 2026 15:07:32 GMT

VijayanPN പ്രമാണം:Figure-26-2-Full-Account-Backup.png അപ്‌ലോഡ് ചെയ്തു

പുതിയ താൾ

26 - 26 – Disaster Recovery

VijayanPN — Mon, 10 Aug 2026 15:06:36 GMT

26.3 The Full Account Backup

←പഴയ രൂപം		20:36, 10 ഓഗസ്റ്റ് 2026-നു നിലവിലുണ്ടായിരുന്ന രൂപം
(ഒരേ ചെയ്ത ഇടയ്ക്കുള്ള 3 നാൾപ്പതിപ്പുകൾ പ്രദർശിപ്പിക്കുന്നില്ല)
വരി 19:		വരി 19:

	The existing installation, its uploaded files, configuration, extensions, customisations and database should therefore be preserved through reliable backups.		The existing installation, its uploaded files, configuration, extensions, customisations and database should therefore be preserved through reliable backups.
	~~[[പ്രമാണം:~~Figure-26-1-Restoration.svg\|~~നടുവിൽ\|ലഘുചിത്രം~~\|~~900x900ബിന്ദു\|'''Figure 26-1 –~~ Disaster Recovery and Restoration Path~~''']]~~		{{Figure
			\|number=26-1
			\|file=Figure-26-1-Restoration.svg \| 900px
			\|title=Disaster Recovery and Restoration Path
			\|caption=The principal recovery paths for restoring Abhiprayavedi after a major failure.
			}}
	== 26.1 The Recovery Principle ==		== 26.1 The Recovery Principle ==
	Abhiprayavedi consists of two major categories of information that must be preserved:		Abhiprayavedi consists of two major categories of information that must be preserved:
വരി 73:		വരി 77:
	== 26.3 The Full Account Backup ==		== 26.3 The Full Account Backup ==
	The Full Account Backup is the principal comprehensive disaster-recovery resource.		The Full Account Backup is the principal comprehensive disaster-recovery resource.

			{{Figure
			\|number=26-2
			\|file=Figure-26-2-Full-Account-Backup.png
			\|900px
			\|title=Full Account Backup
			\|caption=The cPanel Full Backup facility creates an archive of the hosting account's files and configuration. Full account backups are downloaded and preserved outside the hosting account for disaster recovery.
			}}

	The cPanel Backup facility describes a full backup as an archive containing the website's files and configuration. It is intended for keeping a copy of the account or moving the account to another server.		The cPanel Backup facility describes a full backup as an archive containing the website's files and configuration. It is intended for keeping a copy of the account or moving the account to another server.

പ്രമാണം:Figure-26-1-Restoration.svg

VijayanPN — Mon, 10 Aug 2026 13:15:39 GMT

VijayanPN പ്രമാണം:Figure-26-1-Restoration.svg അപ്‌ലോഡ് ചെയ്തു

പുതിയ താൾ

26 - 26 – Disaster Recovery

VijayanPN — Mon, 10 Aug 2026 11:19:28 GMT

←പഴയ രൂപം		16:49, 10 ഓഗസ്റ്റ് 2026-നു നിലവിലുണ്ടായിരുന്ന രൂപം
വരി 1:		വരി 1:
	{{DISPLAYTITLE:Chapter 26 – Disaster Recovery}}		{{DISPLAYTITLE:Chapter 26 – Disaster Recovery}}

	{{DocumentationBreadcrumb\|manual=System Administrator's Manual\|part=V – Maintenance\|chapter=26}}		{{DocumentationBreadcrumb\|manual=System Administrator's Manual\|part=V – Maintenance\|chapter=26}}

	{{DocumentationMetadata\|manual=System Administrator's Manual\|part=V – Maintenance\|chapter=26\|status=Draft}}		{{DocumentationMetadata\|manual=System Administrator's Manual\|part=V – Maintenance\|chapter=26\|status=Draft}}

	= Chapter 26 – Disaster Recovery =		= Chapter 26 – Disaster Recovery =
	The purpose of disaster recovery is to restore Abhiprayavedi when ordinary troubleshooting and maintenance are no longer sufficient.		The purpose of disaster recovery is to restore Abhiprayavedi when ordinary troubleshooting and maintenance are no longer sufficient.

26 - 26 – Disaster Recovery

VijayanPN — Mon, 10 Aug 2026 11:17:08 GMT

'{{DISPLAYTITLE:Chapter 26 – Disaster Recovery}} {{DocumentationBreadcrumb|manual=System Administrator's Manual|part=V – Maintenance|chapter=26}} {{DocumentationMetadata|manual=System Administrator's Manual|part=V – Maintenance|chapter=26|status=Draft}} = Chapter 26 – Disaster Recovery = The purpose of disaster recovery is to restore Abhiprayavedi when ordinary troubleshooting and maintenance are no longer su...' താൾ സൃഷ്ടിച്ചിരിക്കുന്നു

പുതിയ താൾ

{{DISPLAYTITLE:Chapter 26 – Disaster Recovery}}

{{DocumentationBreadcrumb|manual=System Administrator's Manual|part=V – Maintenance|chapter=26}}

{{DocumentationMetadata|manual=System Administrator's Manual|part=V – Maintenance|chapter=26|status=Draft}}

= Chapter 26 – Disaster Recovery =
The purpose of disaster recovery is to restore Abhiprayavedi when ordinary troubleshooting and maintenance are no longer sufficient.

A disaster may involve:

* loss of access to the hosting account;
* serious corruption of the hosting environment;
* loss or corruption of MediaWiki files;
* loss or corruption of the MediaWiki database;
* accidental or incomplete restoration;
* failure of the hosting account requiring a replacement account.

The most important principle is:

'''Disaster recovery normally means restoring the existing Abhiprayavedi installation — not installing MediaWiki again from the beginning.'''

The existing installation, its uploaded files, configuration, extensions, customisations and database should therefore be preserved through reliable backups.
[[പ്രമാണം:Figure-26-1-Restoration.svg|നടുവിൽ|ലഘുചിത്രം|900x900ബിന്ദു|'''Figure 26-1 – Disaster Recovery and Restoration Path''']]

== 26.1 The Recovery Principle ==
Abhiprayavedi consists of two major categories of information that must be preserved:
{| class="wikitable"
!Component
!What it contains
!Principal recovery resource
|-
|MediaWiki files
|MediaWiki core, extensions, skins, images, configuration, custom CSS/JavaScript and other website files
|Home Directory / Full Account Backup
|-
|MediaWiki database
|Pages, revisions, users, permissions, categories, templates and other database content
|MySQL Database Backup / Full Account Backup
|}
A successful recovery therefore requires both the '''application files''' and the '''database'''.

Restoring only the files does not restore the content of the wiki.

Restoring only the database does not restore the complete MediaWiki installation.

== 26.2 First Question: Is the Hosting Account Still Available? ==
When a major failure occurs, the administrator should first determine whether the hosting account itself is still accessible.

=== 26.2.1 Hosting access problem ===
If the website is functioning but the administrator cannot log in to cPanel, this is primarily an '''account-access problem'''.

Examples include:

* forgotten or lost credentials;
* a locked hosting account;
* authentication problems;
* temporary hosting-provider restrictions.

In such cases, contact the hosting provider and restore administrative access.

'''Do not begin a MediaWiki reconstruction merely because cPanel access has been lost.'''

=== 26.2.2 Hosting account failure ===
If the hosting account itself has been lost, seriously corrupted, terminated, or otherwise cannot be recovered normally, contact the hosting provider.

The objective is either:

# restoration of the existing hosting account; or
# provision of a replacement hosting account.

If the provider can restore the account from its own infrastructure backups, this is generally preferable to rebuilding the site manually.

If a replacement hosting account is required, proceed with the backup-based recovery described below.

== 26.3 The Full Account Backup ==
The Full Account Backup is the principal comprehensive disaster-recovery resource.

The cPanel Backup facility describes a full backup as an archive containing the website's files and configuration. It is intended for keeping a copy of the account or moving the account to another server.

For Abhiprayavedi, the full backup is important because it preserves much more than the visible article content.

It may include:

* the MediaWiki core;
* installed extensions;
* skins;
* uploaded images;
* <code>LocalSettings.php</code>;
* custom CSS and JavaScript;
* other MediaWiki files;
* the home directory;
* MySQL databases;
* relevant hosting-account configuration.

The exact contents should be verified against the hosting provider's backup implementation.

=== Important limitation ===
A full cPanel account backup '''cannot normally be restored by the account holder through the ordinary cPanel interface'''.

The cPanel interface provides the facility to generate and download the full backup. Restoration of a full account backup may require the hosting provider or server administrator.

Therefore:

'''A full backup should be downloaded and preserved outside the hosting account.'''

A backup stored only inside the same hosting account is not sufficient protection against complete loss of that account.

== 26.4 Component-Level Recovery Resources ==
In addition to the full account backup, cPanel provides separate recovery resources.

=== 26.4.1 Home Directory Backup ===
The Home Directory backup contains the website files stored within the hosting account.

For Abhiprayavedi, the MediaWiki installation is located within the site's <code>public_html</code> directory under the hosting account.

The relevant files include:

* MediaWiki core;
* <code>extensions/</code>;
* <code>skins/</code>;
* <code>images/</code>;
* <code>resources/</code>;
* <code>vendor/</code>;
* <code>LocalSettings.php</code>;
* custom CSS and JavaScript;
* other MediaWiki and site-specific files.

The exact directory structure should be confirmed against the current installation before a recovery operation.

=== 26.4.2 MySQL Database Backup ===
The MediaWiki database contains the actual wiki data.

It includes, among other things:

* article text;
* revision history;
* users;
* user groups and permissions;
* templates;
* categories;
* page properties;
* logs;
* other MediaWiki database information.

The current Abhiprayavedi database name is recorded in the System Administrator's configuration records.

The database backup should therefore be preserved separately from the website files.

=== 26.4.3 Why both are needed ===
A complete MediaWiki recovery requires both:

'''Website files + MediaWiki database'''

The Home Directory backup alone cannot recreate the database content.

The database backup alone cannot recreate the complete MediaWiki installation.

The Full Account Backup provides the broadest single recovery archive, while the separate Home Directory and MySQL backups provide useful component-level recovery options.

== 26.5 Normal Restoration Path ==
Where the hosting account or replacement account is available, recovery should proceed from the least disruptive method to the most extensive.

=== Step 1 – Establish hosting access ===
Confirm that the administrator can access the hosting control panel.

If necessary, obtain assistance from the hosting provider.

=== Step 2 – Determine what has been lost ===
Before restoring anything, establish whether the problem concerns:

* the hosting account;
* MediaWiki files;
* the database;
* both files and database;
* or only a particular component.

Do not overwrite functioning files or databases unnecessarily.

=== Step 3 – Preserve the current state ===
If the damaged installation is still accessible, preserve whatever remains before beginning restoration.

This may include:

* downloading the current Home Directory;
* downloading the current database;
* preserving <code>LocalSettings.php</code>;
* recording the current MediaWiki version;
* recording installed extensions and other important configuration.

This precaution may be valuable if the initial diagnosis proves incorrect.

=== Step 4 – Restore the required files ===
If MediaWiki files have been lost or corrupted, restore the Home Directory or the relevant files from the available backup.

Where the full account is being restored by the hosting provider, this step may be performed as part of the account restoration.

=== Step 5 – Restore the database ===
Restore the MediaWiki MySQL database from the appropriate database backup.

The database name, database user and permissions must correspond with the restored <code>LocalSettings.php</code> configuration or be adjusted appropriately.

=== Step 6 – Verify the installation ===
Do not consider the recovery complete immediately after the restoration process finishes.

The administrator must verify:

* the main page;
* representative articles;
* Malayalam and English content;
* article revision history;
* user login;
* editorial access;
* images;
* templates;
* categories;
* forms;
* custom CSS and JavaScript;
* important extensions;
* the Editorial Access workflow.

The site should be tested from both desktop and mobile browsers.

== 26.6 Recovery Does Not Normally Mean Reinstalling MediaWiki ==
This distinction is important for future administrators.

If the Home Directory has been successfully restored, the existing MediaWiki installation is already present.

There is normally no reason to:

* download MediaWiki again;
* reinstall every extension;
* recreate the directory structure;
* recreate the uploaded images;
* rebuild the custom CSS;
* recreate <code>LocalSettings.php</code>.

The administrator is restoring the existing installation.

Manual installation becomes necessary only when the original files cannot be recovered or when the existing installation is unusable.

== 26.7 Manual Reconstruction – Last Resort ==
If neither a usable Full Account Backup nor usable component backups are available, Abhiprayavedi may have to be reconstructed manually.

This is the most demanding recovery route.

The reconstruction would generally involve:

# obtaining the appropriate MediaWiki version;
# creating the required hosting directories;
# restoring or reinstalling the required extensions;
# restoring the uploaded images;
# restoring <code>LocalSettings.php</code>;
# restoring custom CSS and JavaScript;
# restoring other site-specific files;
# creating or configuring the MySQL database;
# importing the MediaWiki database dump;
# configuring the database connection;
# verifying file permissions;
# testing MediaWiki;
# testing the extensions and custom functionality;
# testing the editorial workflow.

The System Administrator's Manual, Release Reference Manual and other Abhiprayavedi documentation become especially important during this process.

'''Manual reconstruction should therefore be regarded as the last-resort recovery method, not the normal recovery procedure.'''

== 26.8 Verification After Recovery ==
A technically successful restoration is not necessarily a functionally successful restoration.

The administrator should carry out a structured verification.

=== Basic site test ===
Check:

* Main Page;
* representative Malayalam article;
* representative English article;
* article images;
* categories;
* search;
* navigation;
* mobile display.

=== Editorial test ===
Check:

* Editorial Access;
* administrator login;
* editor login;
* Create Article;
* Drafts;
* Submissions;
* Edit with Form;
* publication workflow.

=== System test ===
Check:

* MediaWiki version;
* installed extensions;
* <code>LocalSettings.php</code>;
* custom CSS;
* custom JavaScript;
* database connectivity;
* uploaded files;
* permissions.

=== Documentation test ===
Check that the System Administrator's Manual and other essential documentation remain available.

If documentation was stored only inside the damaged hosting account, retrieve the separately preserved documentation copy.

== 26.9 Recovery Records ==
Every major recovery should be documented.

Record:
{| class="wikitable"
!Item
!Record
|-
|Date and time
|When the recovery began and ended
|-
|Cause
|Known or suspected cause of the failure
|-
|Hosting status
|Existing account restored or replacement account used
|-
|Backup used
|Full Account, Home Directory, MySQL or other backup
|-
|Backup date
|Date of the backup used
|-
|Restoration actions
|Major steps performed
|-
|Problems encountered
|Errors or unexpected behaviour
|-
|Verification
|Tests performed after restoration
|-
|Final status
|Whether the site was fully restored
|}
These records provide valuable information for future administrators and may reveal weaknesses in the backup or recovery process.

== 26.10 Recovery Priorities ==
When a serious failure occurs, the administrator should avoid attempting to fix everything simultaneously.

The recommended priority is:

# '''Restore control of the hosting environment.'''
# '''Preserve any surviving data.'''
# '''Identify the extent of the failure.'''
# '''Select the appropriate backup.'''
# '''Restore the MediaWiki files.'''
# '''Restore the database.'''
# '''Verify MediaWiki itself.'''
# '''Verify the editorial system.'''
# '''Verify the reader interface.'''
# '''Record the recovery.'''

The objective is not merely to make the homepage appear again.

The objective is to restore a functioning Abhiprayavedi platform.

== 26.11 Backup Discipline and Disaster Readiness ==
Disaster recovery is effective only when usable backups exist before the disaster occurs.

The following principles therefore apply:

* Maintain periodic Full Account Backups.
* Download backups outside the hosting account.
* Maintain accessible copies of the Home Directory and MySQL backups.
* Preserve the current <code>LocalSettings.php</code>.
* Preserve important configuration information.
* Keep the System Administrator's Manual outside the live site as well.
* Record the MediaWiki version and installed extensions.
* Periodically verify that backup files can actually be accessed.
* Do not assume that the existence of a backup file guarantees a successful restoration.

The backup system should be regarded as part of the Abhiprayavedi infrastructure, not merely as an emergency convenience.

== 26.12 The Recovery Test Problem ==
A complete disaster-recovery exercise is difficult to perform on the live Abhiprayavedi site because an actual restoration can itself introduce risk.

A practical approach is therefore to maintain good documentation of the recovery procedure and, where possible, perform limited verification of individual recovery components.

For example:

* verify that a Full Account Backup can be downloaded;
* verify that a Home Directory backup can be downloaded;
* verify that a MySQL backup can be downloaded;
* verify that the backup files are readable and stored outside the hosting account;
* verify that the current MediaWiki version and configuration information are recorded.

A future administrator should not discover the location or nature of the backups for the first time during an actual disaster.

== 26.13 Recovery Completion Checklist ==
{| class="wikitable"
!Check
!Completed
|-
|Hosting access restored
|☐
|-
|Cause or extent of failure identified
|☐
|-
|Surviving data preserved
|☐
|-
|Appropriate backup selected
|☐
|-
|MediaWiki files restored
|☐
|-
|Database restored
|☐
|-
|<code>LocalSettings.php</code> verified
|☐
|-
|Extensions verified
|☐
|-
|Images verified
|☐
|-
|Templates and forms verified
|☐
|-
|Administrator login verified
|☐
|-
|Editorial workflow verified
|☐
|-
|Reader interface verified
|☐
|-
|Mobile interface verified
|☐
|-
|Recovery documented
|☐
|}

== 26.14 Final Principle ==
The long-term survival of Abhiprayavedi does not depend upon preventing every possible failure.

Failures will occur.

What matters is whether the platform can be understood, recovered and restored by someone other than the person who originally built it.

The combination of:

* documented architecture;
* reliable backups;
* preserved configuration;
* separate recovery resources;
* a documented restoration procedure; and
* post-recovery verification

turns a catastrophic failure into a recoverable administrative event.

'''The purpose of disaster recovery is not simply to save files. It is to preserve the ability to restore Abhiprayavedi as a functioning publishing platform.'''

Draft:Documentation/Version 1.0/System Administration Manual

VijayanPN — Mon, 10 Aug 2026 11:16:12 GMT

Part V — Troubleshooting

ഫലകം:CategoryPage

VijayanPN — Sun, 09 Aug 2026 17:06:01 GMT

ഫലകം:CategoryPage താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

<templatestyles src="Template:CategoryPage/styles.css" />
__NOTOC__

<div class="category-page">

<section class="category-hero">
<div class="article-breadcrumb">[[Main Page|🏠 Home]]</div>
<div class="category-page-header">
<h1>{{{CategoryName|{{PAGENAME}}}}}</h1>
<p>ഈ വിഭാഗത്തിലെ ലേഖനങ്ങൾ താഴെ കാണാം</p>
</div>
</section>

<section class="category-highlights">
<div class="category-highlights-grid">
{{#ask:
[[Category:{{{CategoryName|{{PAGENAME}}}}}]]
|?#-=ArticlePage
|?Displayname=Displayname
|?Author=Author
|?Published date=Published date
|?Intro=Intro
|?Image1#200px=Image1
|format=template
|template=ArticleCard
|named args=yes
|limit=2
|sort=Published date
|order=desc
}}
</div>
</section>

<section class="category-focus">

</section>

<section class="category-context">

</section>

<section class="category-archive">
<div class="older-articles-section">
<h3>📚 കൂടുതൽ ലേഖനങ്ങൾ</h3>
<div class="older-articles-list">
{{#ask:
[[Category:{{{CategoryName|{{PAGENAME}}}}}]]
[[ArticlePage::+]]
|?#-=ArticlePage
|?Displayname=Displayname
|?Author=Author
|?Published date=Published date
|format=template
|template=CompactArticleCard
|named args=yes
|ShowImage=no
|limit=50
|offset=2
|sort=Published date
|order=desc
}}
</div>
</div>
</section>
</div>

ഫലകം:CategoryPage/styles.css

VijayanPN — Sun, 09 Aug 2026 17:04:14 GMT

ഫലകം:CategoryPage/styles.css താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

/* ==========================================================
CATEGORY PAGE STYLES
Abhiprayavedi – Editorial Landing Page
Phase B4.2

Layout Regions
1. Editorial Hero
2. Editorial Highlights
3. Editorial Focus
4. Editorial Context
5. Editorial Archive

Note:
This stylesheet defines page layout only.
Reusable component styling belongs to individual templates.
========================================================== */

/* ==========================================================
1. EDITORIAL HERO
========================================================== */

.category-page-header{
background:#edf2f7;
padding:20px;
border-radius:10px;
margin-bottom:30px;
border-left:5px solid #3182ce;
}

.category-page-header h1{
font-family:'Manjari','Meera',sans-serif !important;
margin:0 0 8px;
color:#1a202c;
}

.category-page-header p{
margin:0;
color:#4a5568;
}
/*Hide "... further results" link created by SMW*/
.smw-template-furtherresults{
display:none !important;
}
/* ==========================================================
2. EDITORIAL HIGHLIGHTS
========================================================== */

.category-highlights-grid{
display:grid;
grid-template-columns:repeat(3,1fr);
gap:16px;
padding:12px;
background:#fff;
border-radius:12px;
margin-bottom:15px;
width:100%;
box-sizing:border-box;
}

/* Preserve ArticleCard layout inside the grid */

.category-highlights-grid > div{
display:flex !important;
}

/* ==========================================================
3. EDITORIAL FOCUS
Reserved for future implementation
========================================================== */

.category-focus{
}

/* ==========================================================
4. EDITORIAL CONTEXT
Reserved for future implementation
========================================================== */

.category-context{
}

/* ==========================================================
5. EDITORIAL ARCHIVE
========================================================== */

.older-articles-section{
margin-top:20px;
padding-top:10px;
border-top:2px dashed #e2e8f0;
}

.older-articles-section h3{
font-family:'Manjari',sans-serif !important;
color:#2d3748;
margin-top:15px;
margin-bottom:15px;
}

.older-articles-list{
display:grid;
grid-template-columns:repeat(3,1fr);
gap:20px;
}

.older-articles-list li{
font-family:'Manjari',sans-serif !important;
font-size:1.05em;
margin-bottom:10px;
color:#4a5568;
}

/* ==========================================================
RESPONSIVE
========================================================== */

@media (max-width:768px){

.category-highlights-grid{
grid-template-columns:1fr;
padding:8px;
gap:10px;
}
}
@media (max-width:768px){

.older-articles-list{
grid-template-columns:1fr;
}
}

ഫലകം:CompactArticleCard/styles.css

VijayanPN — Sun, 09 Aug 2026 16:57:53 GMT

ഫലകം:CompactArticleCard/styles.css താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

/* ===================================================
Compact Article Card
Guided Reading Architecture – Phase B2.1
=================================================== */

.compact-article-card {
max-width: 420px;
width: 100%;
margin: 18px 0 28px 0;
border: 1px solid #dde4ea;
border-radius: 12px;
background: #fafbfd;
overflow: hidden;
transition: box-shadow .2s ease;
}

.compact-article-card:hover {
box-shadow: 0 4px 14px rgba(0,0,0,.08);
}

.compact-article-card a {
display:block;
text-decoration:none;
color:inherit;
}

.compact-card-image{
float:left;
margin-right:18px;
}
.compact-card-image img {
display: block;
width: 150px;
height: 150px;
object-fit: cover;
}

.compact-card-content{
overflow:hidden;
padding:18px;
}

.compact-card-title {
font-family: "Manjari","Noto Sans Malayalam",sans-serif;
font-size: 1.25em;
font-weight: 700;
line-height: 1.35;
color: #1f2937;
margin-bottom: 12px;
}

.compact-card-intro {
font-family: "Manjari","Noto Sans Malayalam",sans-serif;
font-size: 1.02em;
line-height: 1.6;
color: #555;
margin-bottom: 14px;
max-height: 5.4em;
overflow: hidden;
}
.compact-card-meta{
font-family: "Manjari","Noto Sans Malayalam",sans-serif;
font-size:.92em;
color:#6b7280;
}

.compact-card-date{
white-space: nowrap;
}
/* ---------- Mobile ---------- */

@media (max-width:768px){

.compact-card-image{
float:none;
width:100%;
margin:0 0 15px 0;
}

.compact-card-image img{
width:100%;
height:auto;
}

.compact-card-image img{
width:100%;
height:auto;
}

.compact-card-content{
padding:16px;
}
}
.compact-article-card::after {
content: "";
display: block;
clear: both;
}

ഫലകം:CompactArticleCard

VijayanPN — Sun, 09 Aug 2026 16:55:48 GMT

ഫലകം:CompactArticleCard താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

<templatestyles src="Template:CompactArticleCard/styles.css" />
<div class="compact-article-card">
{{#ifeq:{{{ShowImage|yes}}}|no||
{{#if:{{{Image1|}}}|
<div class="compact-card-image">
{{{Image1}}}
</div>
}}
}}
<div class="compact-card-content">
<h3 class="compact-card-title">
[[{{{ArticlePage|}}}|{{{Displayname|Untitled}}}]]
</h3>
<div class="compact-card-intro">
{{{Intro|}}}
</div>
<div class="compact-card-meta">
<span class="compact-card-author">
{{#show:{{{Author}}}|?Displayname}}
</span>
<span class="compact-card-date">
{{#if:{{{Published date|}}}|
• {{{Published date}}}
</span>
}}
</div>
</div>
</div>

CreateArticle

VijayanPN — Sun, 09 Aug 2026 16:53:09 GMT

CreateArticle താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

__NOTOC__
<div class="article-breadcrumb"> [[Main Page|🏠 Home]] › [[Editorial Access|Editorial Access]] › [[Editorial Dashboard|Editorial Dashboard]] › '''Create Article''' </div>
<templatestyles src="Template:SubmissionGateway/styles.css" />
<div class="submission-gateway">
<div class="gateway-header">
<div class="gateway-title">📝 ലേഖനം തയ്യാറാക്കുക</div>
<div class="gateway-subtitle">
അഭിപ്രായവേദിയുടെ Publishing Workspace-ലേക്ക് പ്രവേശിക്കുക
</div>
</div>
<div class="gateway-section gateway-author">
<div class="gateway-section-title">
1. രചയിതാവിന്റെ പ്രൊഫൈൽ പരിശോധിക്കുക
</div>
<div class="gateway-help">
ഈ ലേഖനത്തിന്റെ രചയിതാവിനുള്ള Author Profile ഇതിനകം നിലവിലുണ്ടെന്ന് ഉറപ്പാക്കുക.

ഇല്ലെങ്കിൽ ആദ്യം Author Profile തയ്യാറാക്കിയ ശേഷം മാത്രമേ പുതിയ ലേഖനം ആരംഭിക്കാവൂ.

Form:Article-ൽ Author പട്ടികയിൽ ആ പേര് ലഭ്യമാകണം.
</div>
</div>

<div class="gateway-section gateway-naming">

<div class="gateway-section-title">
2. ലേഖനത്തിന്റെ പേജ് നാമം നൽകുക
</div>

<div class="gateway-form">
{{#forminput:form=Article
|button text=ലേഖനം തയ്യാറാക്കുക →
|size=45
|placeholder=ഉദാ: Kerala-Samoohika-Mattam
|query string=namespace=Submissions
}}
</div>

<div class="gateway-help">
മലയാളത്തിലുള്ള ലേഖനത്തിന്റെ പേര് Manglish രൂപത്തിൽ ഇവിടെ നൽകുക.

ലേഖനത്തിന്റെ ശരിക്കുള്ള തലക്കെട്ട് അടുത്ത പേജിലാണ് ചേർക്കേണ്ടത്.

പരമാവധി മൂന്ന് വാക്കുകൾ ഉപയോഗിക്കുക.

ഓരോ വാക്കിന്റെയും ആദ്യ അക്ഷരം Capital Letter ആയിരിക്കണം.

വാക്കുകൾക്കിടയിൽ space നു പകരം Hyphen (-) ഉപയോഗിക്കുക.
</div>

<div class="gateway-rule">
English letters മാത്രം · പരമാവധി മൂന്ന് വാക്കുകൾ · Capital Letter തുടക്കം · Hyphen ഉപയോഗിക്കുക
</div>

<div class="gateway-examples">
<div>
<span>ഭീം ആർമി - ഹിന്ദു വലതിന് ദളിത് വെല്ലുവിളി</span>
<strong>→ Bhim-Army-Hindu</strong>
</div>

<div>
<span>അതിർത്തി കാക്കുന്ന ജവാൻ</span>
<strong>→ Athirthi-Kaakkunna-Javaan</strong>
</div>
</div>

</div>

<div class="gateway-section gateway-preparation">

<div class="gateway-section-title">
3. തുടങ്ങുന്നതിന് മുമ്പ് തയ്യാറാക്കുക
</div>

<div class="gateway-columns">

<div>
<div class="gateway-list-title">ലേഖനം</div>

<ul>
<li>പ്രദർശന നാമം</li>
<li>രചയിതാവ്</li>
<li>ആമുഖം</li>
<li>പൂർണ ലേഖനം</li>
<li>വിഭാഗം</li>
<li>പ്രധാന ആശയങ്ങൾ / ഉദ്ധരണികൾ</li>
<li>ബന്ധപ്പെട്ട ലേഖനം, ഉണ്ടെങ്കിൽ</li>
</ul>
</div>

<div>
<div class="gateway-list-title">ചിത്രങ്ങൾ</div>

<ul>
<li>കുറഞ്ഞ വീതി: 800 px</li>
<li>Landscape preferred (16:9)</li>
<li>JPG, JPEG, PNG, WebP, GIF, SVG</li>
<li>Article-Name-1.jpg</li>
<li>Article-Name-2.jpg</li>
</ul>

</div>
</div>
</div>

<div class="gateway-section gateway-caution">

<div class="gateway-section-title">
4. സമർപ്പിച്ചതിന് ശേഷം
</div>

<div class="gateway-caution-text">

<strong>Save</strong> ചെയ്താൽ ലേഖനം editorial review-നായി <strong>Submissions</strong> വിഭാഗത്തിലേക്ക് പോകും.

ആവശ്യമായ വിവരങ്ങൾ ചേർക്കാനോ തിരുത്താനോ Form വീണ്ടും തുറക്കാം.

ഓരോ Save-ഉം നിലവിലുള്ള submission പുതുക്കും.

</div>

</div>

</div>

Form:Article

VijayanPN — Sun, 09 Aug 2026 16:51:47 GMT

Form:Article താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

<templatestyles src="Form:Article/styles.css" />
<div class="workspace-header">
<div class="workspace-title">Publishing Workspace</div>
</div>
<div class="workspace-intro">Create or edit an article for publication. This workspace guides you through the editorial process. Each section explains what information is required, where it appears after publication and how it should be entered.</div>
'''Editorial Workflow ribbon'''
<div class="workflow-bar">
📄 Publication → 📝 Article → 💬 Presentation Elements → 🖼 Images → 📚 Related Reading → 🌍 Translation → 📋 Editorial Checklist
</div>
Fields marked <span class="required">*</span> are mandatory.
{{{for template|Article|namespace=Submissions}}}
<div class="form-section publication">
<div class="section-title">📄 Publication</div>
<div class="section-purpose">Specify the essential publication details for this article.</div>
<div class="section-significance">These details determine how readers identify, discover and navigate to your article throughout Abhiprayavedi.</div>
<div class="field-block"><div class="field-label">Language <span class="required">*</span></div>
<div class="field-help">Choose the language in which this article is written.</div>
{{{field|Language|input type=dropdown|values=Malayalam (ML),English (EN)|mandatory}}}
</div>
<div class="field-block">
<div class="field-label">Display Title <span class="required">*</span></div>
<div class="field-help">The title displayed to readers.</div>
<div class="field-example">Example: കേരളത്തിന്റെ സാമൂഹിക പരിവർത്തനം</div>
{{{field|Displayname|input type=text|size=80|mandatory}}}
</div>
<div class="field-block">
<div class="field-label">Author <span class="required">*</span></div>
<div class="field-help">Select the author from the existing Author Profiles. Free-text author names are not permitted.</div>
{{{field|Author|input type=dropdown|values from category=Authors|mapping property=Displayname|mandatory}}}
</div>
<div class="field-block">
<div class="field-label">Publication Date <span class="required">*</span></div>
<div class="field-help">Choose the date of publication.</div>
{{{field|Published date|input type=date|default=now|mandatory}}}</div>

<div class="field-block">
<div class="field-label">
Homepage Status <span class="required">*</span>
</div>
<div class="field-help">
Choose how this article should appear on the homepage. Standard is the default for normal publication. Select Top Stories or Featured only when the article is intended for editorial promotion.
</div>
{{{field|HomepageStatus
|input type=radiobutton
|values=Standard,Top Stories,Featured
|default=Standard
|mandatory
}}}
</div>

<div class="field-block">
<div class="field-label">Category <span class="required">*</span></div>
<div class="field-help">Choose the category that best represents the article.</div>
{{{field|Category|input type=dropdown|values=രാഷ്ട്രീയം,സാമ്പത്തികം,കാർഷികം,സമൂഹം,മനുഷ്യാവകാശം,പൌരാവകാശം,ജൻഡർ,ദളിത് /ആദിവാസി,ശാസ്ത്രം,സംസ്കാരം,കല/സാഹിത്യ വിമർശം,വിദേശകാര്യം,ഭാഷ,ചരിത്രം,ഫിലോസഫി,മതം,വിദ്യാഭ്യാസം,പരിസ്ഥിതി,ഭരണം,നിയമം,തൊഴിൽ,അഭിപ്രായം,ചലച്ചിത്രം,ജീവചരിത്രം,അന്താരാഷ്ട്രം,ഊർജം,വ്യവസായം,മാധ്യമം,പൊതുനയം,പാർലമെന്റ്,ഭരണഘടന,തിരഞ്ഞെടുപ്പ്,രാഷ്ട്രീയ ദർശനം,രാഷ്ട്രീയ സിദ്ധാന്തം|mandatory}}}
</div>
</div>
<div class="form-section article">
<div class="section-title">📝 Article</div>
<div class="section-purpose">Write the introduction and main content of the article.</div>
<div class="section-significance">The introduction helps readers understand the article at a glance. The content presents the complete argument or discussion.</div>
<div class="field-block">
<div class="field-label">Intro <span class="required">*</span></div>
<div class="field-help">Write a concise 2–3 sentence summary of the article. This appears on the homepage, category pages, article cards and Continue Reading cards.</div>
<div class="field-example">Summarise the central subject or argument. Do not repeat the display title.</div>
{{{field|Intro|input type=textarea|rows=5|mandatory}}}
</div>
<div class="field-block">
<div class="field-label">Content <span class="required">*</span></div>
<div class="field-help">Begin directly with the article. Do not repeat the title, author or publication date.</div>
{{{field|Content|input type=textarea|rows=25|editor=visualeditor|mandatory}}}
</div>
</div>
<div class="form-section presentation">

<div class="section-title">
💬 Presentation Elements
</div>

<div class="section-purpose">
Choose the ideas that deserve visual emphasis.
</div>

<div class="section-significance">
These elements improve readability and help readers notice important arguments or observations in the article.
</div>

<div class="field-block">
<div class="field-label">
PullQuote
</div>

<div class="field-help">
Select an important statement from the article that deserves visual emphasis.
</div>

<div class="form-note">
Copy the template below and paste it into the Content at the required position. Then copy the selected text from the article and paste it between the template lines.

<pre>{{PullQuote|
text...
}}</pre>

The same selected text may also be copied into Highlight 1 or Highlight 2 when it deserves emphasis in the article sidebar.
</div>
</div>
<div class="field-block">
<div class="field-label">
Highlight 1
</div>
<div class="field-help">
Extract one important idea from the article. It will appear in the article sidebar.
</div>
{{{field|highlight1|input type=textarea|rows=3}}}
</div>
<div class="field-block">
<div class="field-label">
Highlight 2
</div>
<div class="field-help">
Add a second important idea if required. This field is optional.
</div>
{{{field|highlight2|input type=textarea|rows=3}}}
</div>
</div>
<div class="form-section images">
<div class="section-title">
🖼 Images
</div>
<div class="section-purpose">
Add and prepare images used in the article.
</div>
<div class="section-significance">
Images support the article visually. Use clear, relevant images and follow the naming and size standards below.
</div>
<div class="field-block">
<div class="field-label">
Image 1
</div>
<div class="field-help">
The main article image. It appears near the beginning of the article.
</div>
{{{field|Image1|input type=text|uploadable}}}
</div>
<div class="field-block">
<div class="field-label">
Image 1 Caption
</div>
<div class="field-help">
Briefly describe the image where a caption is useful.
</div>
{{{field|Image1_caption|input type=text|size=80}}}
</div>
<div class="field-block">
<div class="field-label">
Image 1 Credit
</div>
<div class="field-help">
Enter the photographer, creator or image source where required.
</div>
{{{field|Image1_credit|input type=text|size=80}}}
</div>
<div class="field-block">
<div class="field-label">
Image 2
</div>
<div class="field-help">
Upload an additional image if required. Insert this image manually at the appropriate position in the article Content.
</div>
{{{field|Image2|input type=text|uploadable}}}
</div>
<div class="field-block">
<div class="field-label">
Image 2 Caption
</div>
<div class="field-help">
Enter the caption used when Image 2 is inserted into the article.
</div>
{{{field|Image2_caption|input type=text|size=80}}}
</div>
<div class="field-block">
<div class="field-label">
Image 2 Credit
</div>
<div class="field-help">
Enter the photographer, creator or image source where required.
</div>
{{{field|Image2_credit|input type=text|size=80}}}
</div>
<div class="field-block">
<div class="field-label">
Image Placement Guide
</div>
<div class="field-help">
For Image 2 and additional images, copy the appropriate example into Content and replace only the filename and caption.
</div>
<div class="form-note">
'''Right Float'''
<pre>[[File:Image-2.jpg|300px|right|Caption]]</pre>
'''Left Float'''
<pre>[[File:Image-2.jpg|300px|left|Caption]]</pre>
'''Centre'''
<pre>[[File:Image-2.jpg|600px|center|Caption]]</pre>
</div>
</div>
<div class="field-block">
<div class="field-label">
Image Naming Convention
</div>
<div class="form-note">
'''Article-specific images'''
<pre>Article-Name-1.jpg
Article-Name-2.jpg
Article-Name-3.jpg</pre>
Use the article name for images specific to one article.
'''Reusable images'''
<pre>Supreme-Court.jpg
Indian-Parliament.jpg
Karl-Marx.jpg</pre>
Use descriptive subject names for generic images that may be reused.
</div>
</div>
<div class="field-block">
<div class="field-label">
Image Standards
</div>
<div class="form-note">
'''Preferred width:''' 1200 px<br>
'''Minimum width:''' 800 px<br>
'''Format:''' JPEG<br>
'''Orientation:''' Landscape preferred
</div>
</div>
</div>
<div class="form-section related">
<div class="section-title">
📚 Related Reading
</div>
<div class="section-purpose">
Connect this article with another relevant article.
</div>
<div class="section-significance">
A carefully selected related article helps readers continue exploring the subject beyond the current article.
</div>
<div class="field-block">
<div class="field-label">
Continue Reading
</div>
<div class="field-help">
Select one related article. It will appear below the article after publication.
</div>
{{{field|ContinueReading|input type=combobox|values from category=Articles}}}
</div>
</div>
<div class="form-section translation">
<div class="section-title">
🌍 Translation
</div>
<div class="section-purpose">
Complete this section only for translated articles.
</div>
<div class="section-significance">
Recording the translator and original source preserves proper attribution and publication information.
</div>
<div class="field-block">
<div class="field-label">
Translator
</div>
<div class="field-help">
Enter the name of the person who translated the article.
</div>
{{{field|translator|input type=text|size=80}}}
</div>
<div class="field-block">
<div class="field-label">
Original Source
</div>
<div class="field-help">
Enter the name of the original publication or source.
</div>
{{{field|source|input type=text|size=80}}}
</div>
<div class="field-block">
<div class="field-label">
Source URL
</div>
<div class="field-help">
Enter the web address of the original article, where available.
</div>
{{{field|source_url|input type=text|size=80}}}
</div>
<div class="field-block">
<div class="field-label">
Permission Notes
</div>
<div class="field-help">
Record any relevant permission, licence or republication information.
</div>
{{{field|permission_note|input type=textarea|rows=3}}}
</div>
</div>
<div class="form-section checklist">
<div class="section-title">
📋 Editorial Checklist
</div>
<div class="section-purpose">
Review the article before saving or publishing.
</div>
<div class="section-significance">
A final review helps identify omissions and presentation errors before the article enters the publication workflow.
</div>
<div class="form-checklist">
<div>✓ Display title verified</div>
<div>✓ Intro completed</div>
<div>✓ Images uploaded</div>
<div>✓ Captions checked</div>
<div>✓ PullQuote inserted, if required</div>
<div>✓ Highlights added, if required</div>
<div>✓ Continue Reading selected</div>
<div>✓ Preview reviewed</div>
</div>
</div>
</div>
{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|cancel}}}
{{{end template}}}

Form:Article/styles.css

VijayanPN — Sun, 09 Aug 2026 16:51:06 GMT

Form:Article/styles.css താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

.workspace-header {
margin-bottom: 1.5rem;
padding: 1.5rem 1.75rem;
border-left: 5px solid #4f81bd;
background: #f7faff;
}

.workspace-title {
font-size: 1.8rem;
font-weight: bold;
margin-bottom: 1rem;
}

.workspace-intro {
margin-bottom: 1.5rem;
}

.workflow-bar {
margin-bottom: 2rem;
}

.form-section {
margin-top: 2rem;
margin-bottom: 2rem;
}

.section-title {
font-size: 1.3rem;
font-weight: bold;
}

.section-purpose {
margin-top: 0.5rem;
}

.section-significance {
margin-top: 0.5rem;
font-style: italic;
}

.required {
color: #b32424;
font-weight: bold;
}

.form-section {
margin: 2rem 0;
padding: 1.5rem 1.75rem;
border: 1px solid #d8dee5;
border-radius: 6px;
}

.form-section.publication {
border-left: 5px solid #4f81bd;
background: #f7faff;
}

.section-title {
font-size: 1.35rem;
font-weight: 700;
margin-bottom: 0.5rem;
}

.section-purpose {
font-size: 1rem;
margin-bottom: 0.4rem;
}

.section-significance {
font-size: 0.95rem;
font-style: italic;
color: #54595d;
}

.field-block {
margin-top: 1.25rem;
padding-top: 1rem;
border-top: 1px solid #eaecf0;
}

.field-label {
margin-bottom: 0.35rem;
font-size: 1rem;
font-weight: 700;
}

.field-help {
margin-bottom: 0.45rem;
color: #54595d;
font-size: 0.92rem;
}

.field-example {
margin-bottom: 0.5rem;
color: #72777d;
font-size: 0.88rem;
font-style: italic;
}

.required {
color: #b32424;
font-weight: 700;
}
.form-section.article {
border-left: 5px solid #5a9367;
background: #f7fbf8;
}
.form-section.presentation {
border-left: 5px solid #c7a83c;
background: #fffdf5;
}

.form-note {
margin-top: 0.6rem;
padding: 0.75rem 1rem;
border-left: 3px solid #a2a9b1;
background: #f8f9fa;
font-size: 0.9rem;
}

.form-note pre {
margin: 0.6rem 0 0;
padding: 0.6rem;
overflow-x: auto;
}

.form-section.images {
border-left: 5px solid #8b6fa8;
background: #faf8fc;
}

.form-section.related {
border-left: 5px solid #718096;
background: #fafbfc;
}

.form-section.checklist {
border-left: 5px solid #a2a9b1;
background: #fbfbfb;
}

.form-checklist {
margin-top: 1rem;
padding: 0.9rem 1.1rem;
border: 1px solid #eaecf0;
border-radius: 4px;
background: #fff;
}

.form-checklist div {
padding: 0.3rem 0;
}

Submissions:Go-Vijnjana-Pareekshakal

SajuA — Sat, 08 Aug 2026 16:21:33 GMT

Submissions:Go-Vijnjana-Pareekshakal

EditorVij — Sat, 08 Aug 2026 16:15:53 GMT

ഫലകം:PullQuote/styles.css

VijayanPN — Sat, 08 Aug 2026 14:20:51 GMT

ഫലകം:PullQuote/styles.css താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

.pullquote {
position: relative;

display:block;

box-sizing:border-box;

margin:1.5em 0;

padding:.9em 1.2em .9em 1.6em;

width: auto;
overflow: hidden;
background:#f9fbfe;

border-left:3px solid #2f65cb;

border-radius:6px;
}
.pullquote::before {
content: "❝";
position: absolute;
top: 0.75em;
left: 0.65em;
font-size: 1.5rem;
line-height: 1;
color: #4b5563;
opacity: .65;
}
.quote-text p{

font-size:1.12rem;

font-weight:500;

line-height:1.5;

color:#222;
}

ഫലകം:PullQuote

VijayanPN — Sat, 08 Aug 2026 14:18:09 GMT

ഫലകം:PullQuote താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

ഫലകം:AuthorCard

VijayanPN — Sat, 08 Aug 2026 14:08:53 GMT

ഫലകം:AuthorCard താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

<templatestyles src="Template:AuthorCard/styles.css" />
<div class="author-card"> {{#if: {{{AuthorPhoto|}}} |
<div class="author-card-photo"> {{{AuthorPhoto|}}} </div>
}}
<h4 class="author-card-name">
[[{{{AuthorPage|}}}|{{{Displayname|}}}]]</h4>
{{#if: {{{AuthorBio|}}} | <div class="author-card-bio"> {{{AuthorBio|}}} </div>
}}
<div class="author-card-profile">[[{{{AuthorPage|}}}|കൂടുതൽ വായിക്കുക →]]</div>
</div>

ഫലകം:ArticleCard/styles.css

VijayanPN — Sat, 08 Aug 2026 14:06:20 GMT

ഫലകം:ArticleCard/styles.css താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

/* ================ ARTICLE CARD STANDARDISED STYLES ================ */

.article-card {
display: flex;
flex-direction: column;
border: 1px solid #e2e8f0;
border-radius: 8px;
margin-bottom: 1.5rem;
background-color: #ffffff;
overflow: hidden;
box-shadow: 0 1px 3px rgba(0,0,0,0.05);
height: 100%;
}

.article-Image1 {
width: 100%;
height: 180px;
overflow: hidden;
background-color: #f7fafc;
display: flex;
justify-content: center;
align-items: center;
}

.article-Image1 img {
width: 100%;
height: 100%;
object-fit: cover;
display: block;
}

/* Informational text wrapper below the image */
.article-info {
padding: 4px 10px 4px 10px ;
display: flex;
flex-direction: column;
flex-grow: 0;
}

/* Title / Displayname section with enforced font styling */
.article-title {
font-family: 'Manjari', 'Meera', 'Rachana', 'Noto Sans Malayalam', sans-serif !important;
font-size: 1.25em;
font-weight: 700;
line-height: 1.4;
margin: 0 0 0.5rem 0;
}

.article-title a {
color: #1a202c;
text-decoration: none;
}

.article-title a:hover {
color: #3182ce;
}

/* Standard compliant text containment replacing non-standard webkit-clamping */
.article-intro-wrapper {
position: relative;
max-height: 4.8em; /* 3 വരികൾക്കായി കൃത്യമായി ക്രമീകരിച്ചത് (1.6em line-height * 4) */
overflow: hidden;
margin-bottom: 4px !important;
}
.article-intro {
font-family: 'Manjari', 'Meera', 'Rachana', 'Noto Sans Malayalam', sans-serif !important;
font-size: 0.95em;
line-height: 1.6em;
color: #4a5568;
margin: 0 !important; /* മീഡിയവിക്കി P ടാഗിന്റെ ഡിഫോൾട്ട് മാർജിൻ പൂർണ്ണമായി ഒഴിവാക്കി */
padding: 0 !important;
}

/* ഓതർ, ഡേറ്റ് എന്നിവ അടങ്ങുന്ന മെറ്റാ റോ */
.article-meta-row {
display: flex;
justify-content: space-between;
align-items: center;
margin-top: 4px !important;
margin-bottom: 0 !important;
padding-top: 0px !important;
font-family: 'Manjari', 'Meera', 'Rachana', 'Noto Sans Malayalam', sans-serif !important;
}

/* മീഡിയവിക്കി ജനറേറ്റ് ചെയ്യാൻ സാധ്യതയുള്ള അനാവശ്യ മാർജിനുകളെ തടയാൻ */
.article-meta-row p,
.article-info p {
margin: 0 !important;
padding: 0 !important;
}

.article-author {
font-size: 0.85em;
font-weight: 600;
color: #6b1f1f;
margin: 0 !important;
}

.article-date {
font-size: 0.8em;
color: #718096;
margin: 0 !important;
white-space: nowrap;
}

/* Optional placeholder class for hidden internal metadata layout */
.author-photo-hidden {
display: none;
}
@media (max-width:768px) {

.article-Image1 {
height: 120px !important;
}

.article-info {
padding: 10px !important;
}
}
@media (max-width: 768px) {

.article-meta-row {
display: flex;
flex-wrap: wrap;
align-items: flex-start;
gap: 0.2em 0.5em;
}
}

ഫലകം:ArticleCard

VijayanPN — Sat, 08 Aug 2026 14:03:33 GMT

ഫലകം:ArticleCard താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

<templatestyles src="Template:ArticleCard/styles.css" />
<div class="article-card">
 {{#if: {{{Image1|}}} | <div class="article-Image1"> {{{Image1}}} </div> }}

<div class="article-info">

<h3 class="article-title">[[{{{ArticlePage|}}}|{{{Displayname|{{{1}}}}}}]]</h3>

{{#if: {{{Intro|}}} |
<div class="article-intro-wrapper">
<p class="article-intro">{{{Intro|}}}</p>
</div>
}}

{{#if: {{{Authorphoto|}}} | <div class="author-photo-hidden">[[File:{{{Authorphoto}}}|20px]]</div> }}

<div class="article-meta-row">
{{#if: {{{Author|}}} |
<span class="article-author">
[[{{{Author}}}|{{#show: {{{Author}}} |?Displayname}}]]
</span>
}}
{{#if: {{{Published date|}}} |
<span class="article-date">{{#time: j F Y | {{{Published date|}}} | ml }}</span>
}}
</div>
</div>
</div>

ഫലകം:Article

VijayanPN — Sat, 08 Aug 2026 13:31:52 GMT

ഫലകം:Article താൾ VijayanPN സംരക്ഷിച്ചു [തിരുത്തുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം) [തലക്കെട്ട് മാറ്റുക=സിസോപ്പുകളെ മാത്രം അനുവദിക്കുന്നു] (അനിശ്ചിതകാലം)

പുതിയ താൾ

<includeonly>__NOTOC__<templatestyles src="Template:Article/styles.css"/>

<div style="display:none">[[Displayname::{{{Displayname|}}}]]
[[ArticlePage::{{FULLPAGENAME}}]]
[[Author::{{{Author|}}}]]
[[Published date::{{{Published date|}}}]]
[[Homepage Status::{{{HomepageStatus|Standard}}}]]
[[ContinueReading::{{{ContinueReading|}}}]]
[[Intro::{{{Intro|}}}]]
[[Image1::File:{{{Image1|}}}]]
[[Category:{{{Category|General}}}]]
{{#set:Published date={{#time:Y-m-d|{{{Published date|}}}}}}}
</div>
{{DISPLAYTITLE:{{{Displayname|No Title Provided}}}}}

<div class="article-header"><div class="article-byline"><span class="author-name">{{#show:{{{Author|}}}|?Displayname}}</span><span class="meta-separator">•</span><span class="article-date">{{#time:j F Y|{{{Published date|}}}|ml}}</span></div></div>

{{#ifeq:{{NAMESPACE}}|Submissions|
<div class="article-breadcrumb">
[[Main Page|🏠 മുഖപ്പേജ്]]
<span class="breadcrumb-separator">›</span>
[[Editorial Access|Editorial Access]]
<span class="breadcrumb-separator">›</span>
[[Editorial Dashboard|Editorial Dashboard]]
<span class="breadcrumb-separator">›</span>
'''Submission'''
</div>
|
<div class="article-breadcrumb">
[[Main Page|🏠 മുഖപ്പേജ്]]
<span class="breadcrumb-separator">›</span>
[[:Category:{{{Category|General}}}|{{{Category|General}}}]]
</div>
}}

<div class="intro-box">{{{Intro|Placeholder: Add a brief 2–3 line introduction here.}}}</div>

<div class="article-sidebar">{{#if:{{{highlight1|}}}|<div class="highlight-box">🔑 {{{highlight1}}}</div>}}{{#if:{{{highlight2|}}}|<hr><div class="highlight-box">💡 {{{highlight2}}}</div>}}</div>

<div class="article-content">{{#if:{{{Image1|}}}|<div class="article-image1">[[File:{{{Image1}}}|360px]]{{#if:{{{Image1_caption|{{{Image1_credit|}}}}}|<div class="image-caption">{{{Image1_caption|}}}{{#if:{{{Image1_credit|}}}|<br><small>ചിത്രം: {{{Image1_credit}}}</small>}}</div>}}</div>}}{{{Content}}}</div>

{{#if:{{{translator|{{{source|}}}}}}|
== Source Attribution ==
Translated by: {{{translator}}}<br>
Original Source: {{{source|}}}<br>
URL: {{{source_url|}}}<br>
Permission: {{{permission_note|}}}
}}

[[Category:{{{Category|General}}}]]

{{#if:{{{ContinueReading|}}}|
<div class="continue-reading">
<h3>സമാനവീക്ഷണങ്ങൾ ഉൾക്കൊള്ളുന്ന ലേഖനങ്ങൾ </h3>
{{#ask:
[[ArticlePage::{{{ContinueReading}}}]]
|?ArticlePage=ArticlePage
|?Displayname=Displayname
|?Intro=Intro
|?Author=Author
|?Image1#150px=Image1
|format=template
|template=CompactArticleCard
|named args=yes
|limit=1
}}
</div>
}}

{{#if:{{{Author|}}}|
<div class="author-profile-bottom"> <h4 class="author-heading">എഴുത്തുകാരൻ / എഴുത്തുകാരി</h4>
{{#ask:
[[{{{Author}}}]]
[[Category:Authors]]
|?#-=AuthorPage
|?Displayname=Displayname
|?AuthorPhoto#120px=AuthorPhoto
|?AuthorBio=AuthorBio
|format=template
|template=AuthorCard
|named args=yes
|limit=1
}}
</div>
}}

<div class="related-articles-section">
<h3 class="related-heading">✨ ഇതേ വിഭാഗത്തിലെ മറ്റ് ലേഖനങ്ങൾ</h3>
<div class="related-articles-grid">
{{#ask:
[[Category:{{{Category|General}}}]]
[[ArticlePage::!{{FULLPAGENAME}}]]
|?#-=ArticlePage
|?Displayname=Displayname
|?Author=Author
|?Published date=Published date
|?Intro=Intro
|?Image1#150px=Image1
|format=template
|template=ArticleCard
|named args=yes
|limit=3
|searchlabel=
|sort=Published date
|order=desc
}}
</div>
</div>

[[Category:Articles]]
{{#ifeq:{{NAMESPACE}}|Submissions|
{{#formlink:
form=Article
|target={{FULLPAGENAME}}
|link text=✏️ Edit with Form
|link type=button
}}
}}
</includeonly>

ഉപയോക്താവ്:AparnaV

VijayanPN — Sat, 08 Aug 2026 12:40:45 GMT

AparnaV എന്ന ഉപയോക്താവിന്റെ സംഘ അംഗത്വം, (ഒന്നുമില്ല) എന്നതിൽ നിന്നു കാര്യനിർവാഹകൻ എന്നതിലേക്ക്, VijayanPN മാറ്റിയിരിക്കുന്നു

ഉപയോക്താവ്:AparnaV

VijayanPN — Sat, 08 Aug 2026 12:39:53 GMT

AparnaV എന്ന ഉപയോക്തൃ അംഗത്വം VijayanPN സൃഷ്ടിച്ചിരിക്കുന്നു, രഹസ്യവാക്ക് ഇമെയിൽ വഴി അയച്ചു

25 - Troubleshooting and Error Diagnosis

VijayanPN — Sat, 08 Aug 2026 12:37:20 GMT

25.1 The Diagnostic Principle

←പഴയ രൂപം		18:07, 8 ഓഗസ്റ്റ് 2026-നു നിലവിലുണ്ടായിരുന്ന രൂപം
(ഒരേ ചെയ്ത ഇടയ്ക്കുള്ള ഒരു നാൾപ്പതിപ്പ് പ്രദർശിപ്പിക്കുന്നില്ല)
വരി 6:		വരി 6:
	\|status=Draft		\|status=Draft
	}}		}}

	= Chapter 25 – Troubleshooting and Error Diagnosis =		= Chapter 25 – Troubleshooting and Error Diagnosis =

വരി 61:		വരി 60:
	\|file=Figure-25.1 Troubleshooting Flowchart.png		\|file=Figure-25.1 Troubleshooting Flowchart.png
	}}		}}
			The flowchart is a practical guide rather than a rigid procedure.

	== 25.2 First Determine the Scope of the Problem ==		== 25.2 First Determine the Scope of the Problem ==