Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I have recently taken ownership of an Wordpress website, after having a long dispute with the previous developer.
Because of this, I want to make sure that he didn't left some malicious code inside - to steal passwords, change things in the database, remove files ....
So the question is that instead of checking each file inside (Wordpress core, plugins, and so on) - what other possibilities I have to make sure that there is no threat? How can one protect himself from an inside attack?
I know that this can be difficult to answer, but maybe you have some past experience with this kind of situations...
If it's a stock installation of Wordpress, you can use "diff" or a similar file-comparison tool to compare your installation against the official distribution to see what changes, if any, have been made.
After you've done that and made sure you understand the purpose of any changes, you'll need to go over the configuration, account settings, and the like to make sure there aren't any backdoors or other security holes deliberately left behind.
Unfortunately the only definitive safe answer I can offer is a fresh install, followed by a copy of TEXT content into the new site. Non-text-content items you want to retain will need to be either rewritten or thoroughly vetted.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
I am totally a beginner to WordPress. I have a html site that needs to be converted to WordPress. And it should be fully customizable. I have seen plenty of tutorials but those didn't help. Anyone who can help?
This is not a great question for SO but FYI you need to consider what your site contains. Is it a bunch of HTML pages each of which represents a page with content or a post with content?
Wordpress is a CMS (content management system). It primarily deals with posts (dated items), pages (static posts), and images (media). Think about how your content in your existing HTML site will map to Wordpress.
Finally think about the rationale to move. There is a trend to move away from CMS / Wordpress to static HTML sites (for performance and security). What would you win out of migrating?
You see, more questions than answers. Keep investigating and come back with specific questions.
There are several options:
Use some online converter, like https://htmltowordpress.io/ ( but I guess you'll have do some tweaks after to suite your needs)
Install clean WordPress on your host and search for some good WordPress theme, that could be tweaked to look like yours original site Front End.
Hire a freelancer do do the work for you, It should't be very expensive :)
First of all, You should have a good knowledge of html,php and css.
You can choose to start with one these two of following options.
1, Creating a new theme.
2, Choosing an exixting theme and updating it.
You can find both the above given options at https://www.elegantthemes.com/blog/tips-tricks/converting-html-sites-to-wordpress-sites
Hope this will help.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
Is it possible to scrape data automatically from websites that require a validation code each time a webpage is accessed? Such as the case when the website shows you a picture of the code and asks you to enter what is shown in the picture. I'm using the rvest package. Is this possible to do?
What you're trying to do is beat CAPTCHAs. That's possible but very hard. This is a spammer's hardest job - to come up with an algorithm smart enough to fill out those fields correctly. It's not something you're supposed to do, the whole point of those validation codes is to prevent access from non-humans. If you're smart and motivated enough to figure out how to answer those questions programatically, you can probably make more money doing that than whatever you're trying to do :)
Some websites offer a direct API, which is the way you're supposed to interact with their data. But getting past a CAPTCHA by scraping is not an easy deed.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
While Single-Page application approach is rising as a web development choice, I still don't understand, practically, how would losing the ability to go back/forward in the browser be an O.K sacrifice? Imagine Facebook without direct page navigation! Is there an essential/direct purpose for SPA I can't get my hands on?
You wont have to give up back button functionality to develop a single page application. HTML5 has a history api (and there's polyfills for older browsers) which allows your to keep back button functioning properly.
The main reason (in my opinion) to go for a single page approach is the more app-like feel it gives you. For example gmail feels more like an app than a web page, and given its purpose, I think that's way it should be too. Another example might be the pixlr online image editor.
Single page approach indeed doesn't suit every purpose, but when you want a webapp to feel just that, instead of a website, then single page might be the way to go.
You mentioned direct navigation in comments, and that's totally doable if it's something that makes sense in your context. Angularjs can do that, and I'm sure pretty much every modern single page framework has a way of implementing this.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am developing a travels related website using cakephp. I have to put some tour itinerary/special vacation campaign etc. on it almost everyday. The template/format remain the same, just the content changes. So, I am guessing that I can use some content management system like Wordpress/Joomla here.
Till now I had been working mainly on static pages only, but from now I will work on including search functions, forums, members area, polls, etc. in the website.
Can somebody tell me if switching to these CMS technologies is a good idea?
Regards
Joomla would be apt for you. Because Its going to be something like a website. Hence you can choose joomla, also there are lot of joomla templates available, you can customise to your needs.
Wordpress would not be right for you since its a blogging tool. Unless until you need blogging functionality you need not have wordpress.
There is also something like drupal,
You may read here for better clarity here
Yes, it is really a good idea. Using already built CMS saves time and increases the customization. For Wordpress, there are thousands of plugin which can transform WP into a CMS.
Also, security will be good if a CMS is used. You will get regular updates for stability.
Check this page: Need a simple CMS. Should I customise an existing CMS or build from scratch?
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
How to make maintenance document for a website? I've created a site using XHTML ,CSS, jQuery etc. it's big site.
Now i have to write a maintenance document for a site for if any changes comes in future related to design, content and functionality then those things will be handled by someone else.
How and what should i keep in maintenance document.
Your maintenance document should contain a high-level design of what each file contains and the general code structure of the project.
For example, if you wrote some javascript to handle certain events, document those and how they interact with the page.
You should also document any logical groupings you've made. If a folder contains all the XHTML for a certain topic, write those down.
Also give a brief explanation of how you used CSS to layout the page. Which classes are where on the page, and which classes or ids are important.
As for the how, I like to set up a Wiki in such cases, for example DokuWiki. They're easy to understand, and in case of DokuWiki there's no database involved, just plain text files.
As to what, (in addition to what Ben S nicely outlines in his answer) I'd cover
The basic technologies used
Any client-side libraries used and their versions
A rundown on the directory structure
The hosting environment, what is configured where, control panel URLs and the like (never actual passwords)
Names and contact data of contacts (Tech support, etc.) plus any experiences with them (how best to reach them, phone, mail, etc.)