1.

INTRODUCTION

1.1 ABSTRACT
Local Services Search Engine Management System (LSSEMS) is a web based application
which helps user to find serviceman in a local area such as maid, tuition teacher, plumber etc.
LSSEMS contain data of serviceman (maid, tuition teacher, plumber etc.). The main purpose
of LSSEMS is to systematically record, store and update the serviceman records.

LSSEMS is a web based application which provides technology based platform to users to take
care of their daily needs. This application manages all critical minor concern. Can help user to
get the serviceman of locality at doorstep. It is a web application which serving as a platform
for users and service providers to interact each other about delivering the desired service. In
this project there are two modules i.e. admin and user.1. Project Title:
Local Service Search Engine Management System.

1
1.2 EXISTING SYSTEM AND LIMITATIONS OF THE EXISTING SYSTEM
Existing System:
The Local Service Search Engine Management System is a digital platform designed to
connect users with local service providers. It facilitates the search for various services such
as plumbing, electrical repairs, tutoring, gardening, and more within a specific geographic
area. Users can search for service providers, view their profiles, read reviews, and contact
them for services.

Limitations of the Existing System:

1. Limited Geographic Coverage:
The existing system may cover only specific regions or cities, limiting its usability for users
in areas not supported by the platform.

2. Limited Service Categories:

The range of service categories might be limited, leaving out niche or specialized services
That users might be looking for.

3. Outdated Information:
Service provider information such as contact details, services offered, and customer
reviews might become outdated, leading to unreliable search results.

4. Limited User Reviews:

Limited or biased user reviews can hinder users from making informed decisions about
Service providers, affecting their overall satisfaction.

5. Mobile Accessibility Issues:

If the platform is not optimized for mobile devices, users might face accessibility issues,
as people rely heavily on smartphones for such services.

6. Security Concerns:
The existing system might lack robust security measures, making it susceptible to data
breaches and privacy concerns, especially if it handles sensitive user information.

2
1.3 NEED FOR THE PROPOSED SYSTEM
The main purpose of LSSEMS to solve the problem of users who search serviceman in
their own locality by providing a platform for users and serviceman (maid, tuition
teacher, plumber etc.).

1.4 SCOPE OF SYSTEM

This web application solve all household problems by providing a platform for Users and
service providers to interact each other about delivering the desired service.

1. User Management:
User registration and login mechanisms.
User profiles with personal details and preferences.
Ability to reset passwords and manage account settings.

2. Service Listings and Search:

Comprehensive service categories and subcategories.
Advanced search functionality based on location, service type, ratings, and reviews.
Service provider listings with detailed information.

3. Reviews and Ratings:

User reviews and ratings for service providers.
Commenting and feedback mechanisms for users to share their experiences.
Moderation to prevent fake reviews.

4. Mobile Optimization:
Responsive design and dedicated mobile apps for iOS and Android platforms.
Ensuring smooth user experience on various devices and screen sizes.

5. Admin Panel:
Dashboard for administrators to monitor user and service provider activities.
User management tools and the ability to ban/unban users or providers.
Content moderation tools to ensure the platform's integrity.

6. Feedback and Improvement Mechanism:

User feedback system to collect suggestions and report issues.

3
1.5 BRIEF DESCRIPTION OF TECHNOLOGY USED

1.5.1 OPERATING SYSTEMS USED (WINDOWS OR UNIX):

Windows Operating System:
1.User-Friendly Interface: Windows operating systems are known for their user-friendly
graphical interfaces, making them accessible to a wide range of users.
2.Compatibility: Windows supports a vast array of software applications, which can be
beneficial if the project requires specific Windows-based software tools.
3.Commercial Support: Windows is a commercial operating system, and users can avail
dedicated support from Microsoft.
4.Common in Desktop Environments: Windows is widely used in desktop environments,
making it a natural choice for projects that heavily involve desktop applications.

1.5.2 DATABASE (IF APPLICABLE):

Database- MySQL
MySQL is a relational database management system based on the Structured Query Language,
which is the popular language for accessing and managing the records in the database. MySQL
is open-source and free software under the GNU license. It is supported by Oracle Company.
MySQL as a RDBMS software provides many things, which are as follows:
It allows us to implement database operations on tables, rows, columns, and indexes.
•It defines the database relationship in the form of tables (collection of rows and columns), also
known as relations. . It provides the Referential Integrity between rows or columns of various
tables.
•It uses many SQL queries and combines useful information from multiple tables for the end-
users.
•MYSQL compiles on a number of platforms.
•MYSQL is free to download and use.
•MYSQL is a database server

4
 2. PROPOSED SYSTEM
2.1 STUDY OF SIMILAR SYSTEMS
1. Overview of Similar Systems:
Introduce and describe the existing local service search engine platforms you are studying.
Provide information on their target audience, geographic coverage, and the range of services
they offer.

2. Features and Functionalities:

Detail the features and functionalities offered by these platforms. Compare them with the
features planned for your system.
Identify unique features that set each platform apart and analyze how they enhance user
experience.

3. User Experience:
Analyze the user interface and user experience design of similar systems.
Consider the ease of navigation, search efficiency, and overall user satisfaction.

4. User Feedback and Reviews:

Research user feedback and reviews on these platforms. Identify common praises and
complaints from users.
Analyze how these platforms respond to user feedback and resolve issues.

5. Challenges Faced:
Identify challenges faced by similar systems. This could include technical challenges, user
adoption issues, or legal and regulatory hurdles.
Understand how these challenges were addressed and what lessons can be learned from their
solutions.

6. Conclusion and Insights:

Summarize the key findings from your study of similar systems.
Provide insights into what worked well for these platforms and what pitfalls your project should
avoid based on their experiences.
By thoroughly researching and analyzing similar systems, you can gain valuable insights that
will inform the design, development, and implementation of your Local Service Search Engine
Management System, increasing its chances of success in the competitive market.

5
2.2FEASIBILITY STUDY
The very first phase in any system developing life cycle is preliminary investigation. The
feasibility study is a major part of this phase. A measure of how beneficial or practical the
development of any information system would be to the organization is the feasibility study.

Operational Feasibility-
The site will reduce the time consumed to maintain manual records and is not tiresome and
cumbersome to maintain the records. Hence operational feasibility is assured.

Technical Feasibility-
1.At least 2.42 GHz Intel Processor.
2.At least 2GB RAM.
3.14.4 kbps or higher modem.
4.A video graphics card.
5.At least 3 MB free space.

Economic Feasibility-
Once the hardware and software requirements get fulfilled, there is no need for the user of our
system to spend for any additional overhead. For the user, the web site will be economically
feasible in the following aspects:
1. The web site will reduce a lot of paper work. Hence the cost will be reduced.
2. Our web site will reduce the time that is wasted in manual processes.
3. The storage and handling problems of the registers will be solved.

6
2.3 OBJECTIVES OF PROPOSED SYSTEM
1. Facilitate Efficient Service Discovery:
Enable users to easily find local service providers based on their specific needs, location, and
preferences.

2. Enhance User Experience:

Create an intuitive and user-friendly interface for both service seekers and providers, ensuring
seamless navigation and interaction.

3. Provide Comprehensive Service Information:

Offer detailed service provider profiles, including services offered, rates, availability, and
customer reviews, allowing users to make informed decisions.

4. Ensure Scalability and Performance:

Design the system to handle a growing user base and increasing service provider registrations
while maintaining optimal performance.

7
2.4 FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS
1. User Management:
1) User registration and login.
2) User profiles with personal information and preferences.
3) Account management (password reset, account deletion).

2. Service Provider Management:

1) Service provider registration and approval process.
2) Service provider profiles showcasing services, rates, availability, and reviews.
3) Verification mechanisms for service provider authenticity.

3. Service Listings and Search:

1) Comprehensive service categories and subcategories.
2) Advanced search functionality based on location, service type, ratings, and reviews.
3) Service provider listings with detailed information.

4. Reviews and Ratings:

1) User reviews and ratings for service providers.
2) Commenting and feedback mechanisms for users to share experiences.
3) Moderation to prevent fake reviews.

5. Admin Panel:
1. Dashboard for administrators to monitor user and service provider activities.
2. User management tools and ability to ban/unban users or providers.
3. Content moderation tools to ensure platform integrity.

8
Non-Functional Requirements for Local Area Search Engine Management System:

Performance:
1) The system should handle concurrent user requests efficiently without significant delays.
2) Response times for search queries and booking requests should be minimal.

Scalability:
1) The system should be scalable to accommodate a growing user base and increasing service
provider registrations.

Security:
1. Secure user data storage and transmission using encryption techniques.
2. Protection against common web vulnerabilities such as SQL injection, cross-site scripting
(XSS), and CSRF attacks.

Usability:
1. Intuitive user interface with easy navigation for both service seekers and providers.
2. Mobile responsiveness for access via smartphones and tablets.

Reliability:
1. The system should be available 24/7 with minimal downtime for maintenance.
2. Data backup and recovery mechanisms to prevent data loss.

Supportability:
1. Logging and monitoring tools for identifying and resolving issues promptly.
2. Regular software updates and patches to address bugs and security vulnerabilities.

9
2.5 USERS OF SYSTEM

1. Service Seekers:
Individuals: People seeking local services for their personal needs, such as plumbing,
Electrical repairs, tutoring, etc.
Businesses: Companies looking for specific services to maintain their infrastructure or
enhance their operations.
Students: Individuals seeking tutors or educational services within their local area.
Homeowners: People in need of household services like gardening, cleaning, or pest control.

2. Service Providers:
Individual Professionals: Freelancers and independent professionals offering services in
various fields.
Local Businesses: Brick-and-mortar stores or businesses providing specialized services to
the local community.
Service Agencies: Companies offering a range of services through a team of professionals.

10
2.6 MODULE SPECIFICATION
Admin
1. Admin Setting: In this section, admin can update his/her profile, Change password and
logout.
2. Dashboard: In this section, admin can briefly view total number of category and total number
of person.
3. Service Category: In this section, admin can manage category (Add/Update).
4. Person List: In this section, admin can manage person (Add/Update).
5. Pages: In this section admin can manage about us and contact us pages.

Admin can update his profile, change password and recover password.

User
1. Home Page: User can visit home page and view category wise serviceman details.
2. Categories: User can view category wise serviceman details.
3. About Us: User sees the details of website administrator.
4. Contact Us: User can administrator.

Service Category
1. Add Category: Admin can add different category of workers.
2. Manage Category: Admin can manage all type of workers.

Person List
1. Add Person: Admin can add different persons in system.
2. Manage Person: Admin can manage persons in system.

11
 3. SYSTEM ANALYSIS AND DESIGN
3.1 ENTITY RELATIONSHIP DIAGRAM
The Entity-Relationship (ER) model was originally proposed by Peter in 1976 [Chen76] as a
way to unify the network and relational database views. Simply stated the ER model is a
conceptual data model that views the real world as entities and relationships. A basic
component of the model is the Entity-Relationship diagram which is used to visually represent
data objects. Since Chen wrote his paper the model has been extended and today it is commonly
used for database design for the database designer, the utility of the ER model is:
 It maps well to the relational model. The constructs used in the ER model can easily be
transformed into relational tables.
 It is simple and easy to understand with a minimum of training. Therefore, the model
can be used by the database designer to communicate the design to the end user.
 In addition, the model can be used as a design plan by the database developer to
implement a data model in specific database management software.

12
3.2 Use Case Diagram:
Use case diagrams model behavior within a system and help the developers understand of what
the user require. The stick man represents what's called an actor.

Use case diagram can be useful for getting an overall view of the system and clarifying who
can do and more importantly what they can't do.

Use case diagram consists of use cases and actors and shows the interaction between the use
case and actors.

 The purpose is to show the interactions between the use case and actor.
 To represent the system requirements from user's perspective.
 An actor could be the end-user of the system or an external system.

13
3.3 Class Diagram:
A description of set of objects that share the same attributes, operations, relationships, and
semantics.

14
3.4 Sequence Diagram:

3.5 Component Diagram:

15
3.6 Activity Diagram:

16
3.7 TABLE SPECIFICATION [DATA DICTIONARY]
TABLE:
Admin Table:
This store admin personal and login details.
Name Type Null Default Comments Extra
ID int(10) No None AUTO_INCREMENT
AdminName varchar(50) Yes NULL
UserName Varchar(50) Yes NULL
MobileNumber int(10) Yes NULL
Email Varchar(120) Yes NULL
Password Varchar(200) Yes NULL
AdminRegDate timestamp Yes Current_timestamp()

Category Table:
Name Type Null Default Comments Extra
ID int(10) No None AUTO_INCREMENT
Category Varchar(120) Yes NULL
CreationDate timestamp Yes Current_timestamp()

Person Table:
Name Type Null Default Comments Extra
ID int(10) No None AUTO_INCREMENT
Category Varchar(200) Yes NULL
Name Varchar(200) Yes NULL
Picture Varchar(200) Yes NULL
MobileNumber int(10) Yes NULL
Address mediumtext Yes
RegDate timestamp Yes Current_timestamp()

Pages Table:
Name Type Null Default Commen Extra
ts
ID int(10) No None AUTO_INCREMENT
PageType Varchar(50) Yes NULL
PageTitle Varchar(200) Yes NULL
PageDescription mediumtext Yes
Email Varchar(200) Yes NULL
MobileNumber int(10) Yes NULL
UpdationDate timestamp No Current_timestamp() ON UPDATE
CURRENT_TIMEST
AMP()

17
3.11 USER INTERFACE DESIGN AND REPORTS
Home Page :

Categories :

18
About Us :

Contact Us :

19
Admin Login :

Dashboard :

20
Add Category :

Manage Category :

21
Update Category :

Add Person :

22
Manage Person :

Update Person :

23
Contact Us :

Update Admin :

24
 4. Drawbacks And Limitations
1. Limited Geographic Coverage:
The existing system may cover only specific regions or cities, limiting its usability for users
In areas not supported by the platform.

2. Limited Service Categories:

The range of service categories might be limited, leaving out niche or specialized services
That users might be looking for.

3. Outdated Information:
Service provider information such as contact details, services offered, and customer
Reviews might become outdated, leading to unreliable search results.

4. Limited User Reviews:

Limited or biased user reviews can hinder users from making informed decisions about
Service providers, affecting their overall satisfaction.

5. Mobile Accessibility Issues:

If the platform is not optimized for mobile devices, users might face accessibility issues,
As people rely heavily on smartphones for such services.

6. Security Concerns:
The existing system might lack robust security measures, making it susceptible to data
Breaches and privacy concerns, especially if it handles sensitive user information.

5. PROPOSED ENHANCEMENT

1. User Management:
User registration and login mechanisms.
User profiles with personal details and preferences.
Ability to reset passwords and manage account settings.

2. Service Listings and Search:

Comprehensive service categories and subcategories.
Advanced search functionality based on location, service type, ratings, and reviews.
Service provider listings with detailed information.

3. Reviews and Ratings:

User reviews and ratings for service providers.
Commenting and feedback mechanisms for users to share their experiences.
Moderation to prevent fake reviews.

25
 6. CONCLUSION

This Application provides an online version of Local Service System which will benefit the
system administrator who wants to maintain records of serviceman and also help to users who
search serviceman according to his/her requirement in their own locality.

It makes entire process online and can generate reports.

The Application was designed in such a way that future changes can be done easily. The
following conclusions can be deduced from the development of the project.
 Automation of the entire system improves the productivity.
 It provides a friendly graphical user interface which proves to be better when compared
to the existing system.
 It gives appropriate access to the authorized users depending on their permissions.
 It effectively overcomes the delay in communications.
 Updating of information becomes so easier.
 System security, data security and reliability are the striking features.
 The System has adequate scope for modification in future if it is necessary.

7. Bibliography and References:

For PHP:
1. https://www.w3schools.com/php/default.asp
2. https://www.sitepoint.com/php/
3. https://www.php.net/
For MySQL:
1. https://www.mysql.com/
2. http://www.mysqltutorial.org
For XAMPP:
1. https://www.apachefriends.org/download.html
2. Wangkhem, K., & Joshi, K. IOT FOR HEALTHCARE AND ITS CHALLENGES.
International Educational Journal of Science and Engineering (IEJSE) -Volume, 1.

26
 8. ANNEXURES
System Testing
The goal of the system testing process was to determine all faults in our project. The program
was subjected to a set of test inputs and many explanations were made and based on these
explanations it will be decided whether the program behaves as expected or not. Our Project
went through two levels of testing
1. Unit testing
2. Integration testing

Unit Testing
Unit testing is commenced when a unit has been created and effectively reviewed. In order to
test a single module we need to provide a complete environment i.e. besides the section we
would require
1. The procedures belonging to other units that the unit under test calls
2. Non local data structures that module accesses
3. A procedure to call the functions of the unit under test with appropriate parameters

1. Test for the admin module

➤ Testing admin login form-This form is used for log in of administrator of the system. In
this form we enter the username and password if both are correct administration page will open
otherwise if any of data is wrong it will get redirected back to the login page and again ask the
details.

➤ Report Generation- admin can generate report from the main database.

27
 9. SAMPLE CODE
About.php
<?php
session_start();
error_reporting(0);
include('includes/dbconnection.php');
?>
<!DOCTYPE html>
<html>
<head>

<title>LSSEMS | About Us</title>

<!--================================BOOTSTRAP STYLE
SHEETS================================-->

<link rel="stylesheet" type="text/css" href="bootstrap/css/bootstrap.min.css">

<!--================================ Main STYLE

SHEETs====================================-->

<link rel="stylesheet" type="text/css" href="css/style.css">

<link rel="stylesheet" type="text/css" href="css/menu.css">
<link rel="stylesheet" type="text/css" href="css/color/color.css">
<link rel="stylesheet" type="text/css" href="assets/testimonial/css/style.css" />
<link rel="stylesheet" type="text/css" href="assets/testimonial/css/elastislide.css" />
<link rel="stylesheet" type="text/css" href="css/responsive.css">

<!--
================================FONTAWESOME=====================
=====================-->

<link rel="stylesheet" type="text/css" href="css/font-awesome.css">

<!--================================GOOGLE
FONTS=========================================-->

<link href='https://fonts.googleapis.com/css?family=Montserrat:400,700' rel='stylesheet'

type='text/css'>
<link href='https://fonts.googleapis.com/css?family=Lato:300,400,700,900' rel='stylesheet'
type='text/css'>

<!--================================SLIDER REVOLUTION
=========================================-->

28
 <link rel="stylesheet" type="text/css" href="assets/revolution_slider/css/revslider.css"
media="screen" />

</head>
<body>
<div class="preloader"><span class="preloader-gif"></span></div>
<div class="theme-wrap clearfix">
<!--================================responsive log and
menu==========================================-->
<div class="wsmenucontent overlapblackbg"></div>
<div class="wsmenuexpandermain slideRight">
<a id="navToggle" class="animated-arrow slideLeft"><span></span></a>
<a href="#" class="smallogo"><img src="images/logo.png" width="120" alt=""
/></a>
</div>
<!--
================================HEADER===========================
===============-->
<?php include_once('includes/header.php');?>

<!--================================PAGE
TITLE==========================================-->
<div class="page-title-wrap bgorange-1 padding-top-30 padding-bottom-30"><!--
section title -->
<h4 class="white">About Us</h4>
</div><!-- section title end -->
<div class="sc-page"><!--sc-page-->
<!--================================PRICING PLAN SECTION
1==========================================-->

<section class="pricing-section padding-top-70 padding-bottom-40">

<div class="container"><!-- section container -->
<div class="row pricing-wrap style-2 clearfix">

<div class="col-xs-12 col-sm-4 col-md-4 col-lg-4">

<?php
$sql="SELECT * from tblpage where PageType='aboutus'";
$query = $dbh -> prepare($sql);
$query->execute();
$results=$query->fetchAll(PDO::FETCH_OBJ);

$cnt=1;
if($query->rowCount() > 0)
{
foreach($results as $row)
{ ?>

29
 <STRONG style="color: black"><?php echo $row-
>PageTitle;?></STRONG>
<p style="padding-right: 50px"><?php echo $row-
>PageDescription;?></p>
</div><?php $cnt=$cnt+1;}} ?>
<div class="col-xs-12 col-sm-8 col-md-8 col-lg-8"><!-- .pricing -->
<div class="pricing shadow-1 clearfix">
<img src="images/about.png" height="400" width="800" alt="" />
</div>
</div><!-- pricing end -->

</div><!-- .row pricing end -->

</div><!-- container end -->
<?php include_once('includes/footer.php');?>
</div>

<!--
================================JQuery=============================
==============-->

<script type="text/javascript" src="js/jquery-1.11.3.min.js"></script>

<script src="js/jquery.js"></script><!-- jquery 1.11.2 -->
<script src="js/jquery.easing.min.js"></script>
<script src="js/modernizr.custom.js"></script>

<!--
================================BOOTSTRAP========================
===================-->

<script src="bootstrap/js/bootstrap.min.js"></script>

<!--
================================NAVIGATION=======================
====================-->

<script type="text/javascript" src="js/menu.js"></script>

<!--================================SLIDER
REVOLUTION===========================================-->

<script type="text/javascript" src="assets/revolution_slider/js/revolution-slider-

tool.js"></script>
<script type="text/javascript" src="assets/revolution_slider/js/revolution-
slider.js"></script>

30
 <!--
================================MAP==============================
=============-->

<script type="text/javascript"
src="https://maps.googleapis.com/maps/api/js?key=AIzaSyBueyERw9S41n4lblw5fVPAc9U
qpAiMgvM&amp;sensor=false"></script>
<script type="text/javascript" src="js/map.js"></script>
<!-- map with geo locations -->

<script type="text/javascript" src="js/jquery.mapit.js"></script>

<script src="js/initializers.js"></script>

<!--================================OWL
CARESOUL=============================================-->

<script src="js/owl.carousel.js"></script>
<script src="js/triger.js" type="text/javascript"></script>

<!--================================FunFacts
Counter===========================================-->

<script src="js/jquery.countTo.js"></script>

<!--================================jquery
cycle2=============================================-->

<script src="js/jquery.cycle2.min.js" type="text/javascript"></script>

<!--
================================waypoint============================
===============-->

<script type="text/javascript" src="js/jquery.waypoints.min.js"></script><!-- Countdown

JS FILE -->

<!--
================================RATINGS===========================
================-->

<script src="js/jquery.raty-fa.js"></script>
<script src="js/rate.js"></script>

<!--================================ testimonial
===========================================-->
<script id="img-wrapper-tmpl" type="text/x-jquery-tmpl">

<div class="rg-image-wrapper">

31
 <div class="rg-image"></div>
<div class="rg-caption-wrapper">
<div class="rg-caption" style="display:none;">
<p></p>
<h5></h5>
<div class="caption-metas">
<p class="position"></p>
<p class="orgnization"></p>
</div>
</div>
</div>
<div class="clear"></div>
</div>
</script>
<script type="text/javascript" src="assets/testimonial/js/jquery.tmpl.min.js"></script>
<script type="text/javascript" src="assets/testimonial/js/jquery.elastislide.js"></script>
<script type="text/javascript" src="assets/testimonial/js/gallery.js"></script>

<!--================================custom
script===========================================-->

<script type="text/javascript" src="js/custom.js"></script>

</body>
</html>

Custom.js
"use strict";
/*-----------------------------------
Quick Mobile Detection
-----------------------------------*/

var isMobile = {
Android: function() {

return navigator.userAgent.match(/Android/i);
},
BlackBerry: function() {

return navigator.userAgent.match(/BlackBerry/i);
},
iOS: function() {

return navigator.userAgent.match(/iPhone|iPad|iPod/i);
},
Opera: function() {

32
 return navigator.userAgent.match(/Opera Mini/i);
},
Windows: function() {

return navigator.userAgent.match(/IEMobile/i);
},
any: function() {

return (isMobile.Android() || isMobile.BlackBerry() || isMobile.iOS() || isMobile.Opera()

|| isMobile.Windows());
}
};

/*-- Page preloader --*/

$(window).load(function(){
$('.preloader').delay(2000).fadeOut(1000);
});

/*-----------------------------------
REVOLUTION Slider + Shop tabs +
-----------------------------------*/
$(document).ready(function() {
$('.revolution-slider').revolution(
{
dottedOverlay:"none",
delay:6000,
startwidth:1170,
//startheight:windowsHeight,
startheight:740,
onHoverStop:"on",
hideThumbs:0,
fullWidth:"on",
fullScreen: 'off',
forceFullWidth:"off",
navigationType:"none",
shadow:0,
spinner:"spinner4",
hideTimerBar:"on"

});

/*-- listing detail page tabs --*/

$('.tabs .tab-link').on('click', function(){

var tab_id = $(this).attr('data-tab');
var map;
$('.tabs .tab-link').removeClass('current');

33
 $('.tab-content').removeClass('current');

$(this).addClass('current');
$("#"+tab_id).addClass('current');
if(tab_id === 'tab-2'){

init();
}
});

/*-- onepage active menu --*/

$('ul.menu li a').on('click', function() {

var $this = $(this);
$this.parent().siblings().removeClass('active').end().addClass('active');

});

$('.view-switcher ul li').on('click',function(e) {
if ($(this).hasClass('listview')) {
$('.listing-main').removeClass('gridview').addClass('listview');
}
else if($(this).hasClass('gridview')) {
$('.listing-main').removeClass('listview').addClass('gridview');
}
});
$('.view-switcher ul li').on('click',function(e) {
if ($(this).hasClass('listview')) {
$('.view-switcher ul li.gridview').removeClass('active');
$('.view-switcher ul li.listview').addClass('active');
}
else if($(this).hasClass('gridview')) {
$('.view-switcher ul li.listview').removeClass('active');
$('.view-switcher ul li.gridview').addClass('active');
}
});

$( "#slider-range-min" ).slider({
range: "min",
value: 700,
min: 1,
max: 1000,
slide: function( event, ui ) {
$( "#amount" ).val( "$" + ui.value );
}
});
$( "#amount" ).val( "$" + $( "#slider-range-min" ).slider( "value" ) );

34
 /*-----------------------------------
FUNFACTSs
-----------------------------------*/
$('.count').waypoint(function() {
// start all the timers
$('.count').each(count);

function count(options) {

var $this = $(this);

options = $.extend({}, options || {}, $this.data('countToOptions') || {});
$this.countTo(options);
}
},
{
offset: '70%', // middle of the page
triggerOnce: true
});

});

Addcategory.php
<?php
session_start();
error_reporting(0);
include('includes/dbconnection.php');
if (strlen($_SESSION['lssemsaid']==0)) {
header('location:logout.php');
} else{
if(isset($_POST['submit']))
{

$lssemsaid=$_SESSION['lssemsaid'];

$category=$_POST['category'];

$sql="insert into tblcategory(Category)values(:category)";

$query=$dbh->prepare($sql);
$query->bindParam(':category',$category,PDO::PARAM_STR);
$query->execute();

$LastInsertId=$dbh->lastInsertId();
if ($LastInsertId>0) {
echo '<script>alert("Category has been added.")</script>';
echo "<script>window.location.href ='add-category.php'</script>";
}
else
{

35
 echo '<script>alert("Something Went Wrong. Please try again")</script>';
}

?>
<!DOCTYPE html>
<html>
<head>

<title>Local Services Search Engine Mgmt System | Add Category</title>

<!-- Font Awesome -->

<link rel="stylesheet" href="plugins/fontawesome-free/css/all.min.css">
<!-- Ionicons -->
<link rel="stylesheet"
href="https://code.ionicframework.com/ionicons/2.0.1/css/ionicons.min.css">
<!-- Theme style -->
<link rel="stylesheet" href="dist/css/adminlte.min.css">
<!-- Google Font: Source Sans Pro -->
<link href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:300,400,400i,700"
rel="stylesheet">
</head>
<body class="hold-transition sidebar-mini">
<div class="wrapper">
<?php include_once('includes/header.php');?>

<?php include_once('includes/sidebar.php');?>

<!-- Content Wrapper. Contains page content -->

<div class="content-wrapper">
<!-- Content Header (Page header) -->
<section class="content-header">
<div class="container-fluid">
<div class="row mb-2">
<div class="col-sm-6">
<h1>Add Category</h1>
</div>
<div class="col-sm-6">
<ol class="breadcrumb float-sm-right">
<li class="breadcrumb-item"><a href="dashboard.php">Home</a></li>
<li class="breadcrumb-item active">Add Category</li>
</ol>
</div>
</div>
</div><!-- /.container-fluid -->

36
 </section>

<!-- Main content -->

<section class="content">
<div class="container-fluid">
<div class="row">
<!-- left column -->
<div class="col-md-12">
<!-- general form elements -->
<div class="card card-primary">
<div class="card-header">
<h3 class="card-title">Add Category</h3>
</div>
<!-- /.card-header -->
<!-- form start -->
<form role="form" method="post">
<div class="card-body">
<div class="form-group">
<label for="exampleInputEmail1">Category</label>
<input type="text" class="form-control" id="category" name="category"
placeholder="Category" required="true">
</div>

</div>

<div class="card-footer">
<button type="submit" class="btn btn-primary" name="submit">Add</button>
</div>
</form>
</div>
<!-- /.card -->

</div>
<!--/.col (left) -->
<!-- right column -->

</div>
<!-- /.row -->
</div><!-- /.container-fluid -->
</section>
<!-- /.content -->
</div>
<!-- /.content-wrapper -->

<?php include_once('includes/footer.php');?>

<!-- Control Sidebar -->

<aside class="control-sidebar control-sidebar-dark">

37
 <!-- Control sidebar content goes here -->
</aside>
<!-- /.control-sidebar -->
</div>
<!-- ./wrapper -->

<!-- jQuery -->

<script src="plugins/jquery/jquery.min.js"></script>
<!-- Bootstrap 4 -->
<script src="plugins/bootstrap/js/bootstrap.bundle.min.js"></script>
<!-- bs-custom-file-input -->
<script src="plugins/bs-custom-file-input/bs-custom-file-input.min.js"></script>
<!-- AdminLTE App -->
<script src="dist/js/adminlte.min.js"></script>
<!-- AdminLTE for demo purposes -->
<script src="dist/js/demo.js"></script>
<script type="text/javascript">
$(document).ready(function () {
bsCustomFileInput.init();
});
</script>
</body>
</html>
<?php } ?>

38