Have you heard about zippykid ?
I see one of the site is having the following CDN urls in wordpress
uegbwbxgk1hqwla1-zippykid.netdna-ssl.com
How can I disable this CDN and use the default wordpress urls ?
My name is Roberto Villarreal and I am a part of the Pressable team (formerly known as ZippyKid).
These CDN URLs are automatically put into place for customers through a mu-plugin called wp-stack-cdn.php
This file is inside /wp-content/mu-plugins/ alongside others that are a part of Pressable services.
If you want to get rid of these CDN URLs, you should remove the wp-stack-cdn.php plugin and that will take care of it.
I would advise, however, that if you are a moving a site away from the service, that you follow this knowledge base article:
http://kb.pressable.com/pressable-tutorials/move-site-pressable/
This will help ensure you do not run into any other conflicts or issues with plugins that we have in place for use on our services.
Hope this helps!
Related
I want to make a website using Next.js but I want to use WordPress for marketing pages. Let's say I want to use WordPress for a path example.com/sales and Next.js for others. I thought it could be done with load balancing but I'm new to this topic and not sure what I should do. How do I do that?
I think what you are looking for is called incremental adoption. Basically if a certain path is not part of your nextjs app, the traffic falls back to the specified url.
here are the official docs
Our drupal 7 site infected with this link :
https://click.clickanalytics208.com/s_code.js?cid=240&v=73a55f6de3dee2a751c3
Our google ads has been blocked by google due to this link.
We made:
All .js files immutable for same link;
Checked all code and database for same link.
But this didn't solve the issue.
Check your database it maybe infected;
Check contrib modules if you check customs;
Check media it may be infected too;
Try to disable all modules and go to standard theme (if it's production and you have opportunity put to maintenance mode).
Try to find not exactly this js, try to find executor of it.
This specific scripts are added within php files, many times hidden within core files. Also, requesting Google to delist your site might help if you got rid of malicious embedded scripts.
Ping me if you need further help.
I'm researching to see if building a full website for a hotel be a good idea to do on WordPress.
I read that wordpress is okay but there are better options.
I want to design and code my own front end look to the website, but have the backend on a stable platform that can take all the reservations seamlessly.
My main concern is to be able to have a backup of all the files and easily switch to another server in case something goes wrong.
I can host the website on my server or host with the service you suggest that comes with the platform all together.
Any ideas and/or suggestions are greatly appreciated!
There are other options, no doubt, but yes, it can and is really possible to build it using WordPress as CMS.
If you want to design and code your own theme, you'll need to study the WordPress Theme Structure and, since you'll build it by yourself, you'll also need to develop plugins to create custom post types (aka CPT) to make the hotel management easier on the WP back-end.
About the theme structure, files, child themes and everything, I'd recommend you to read https://codex.wordpress.org/Theme_Development
About the plugins development: https://developer.wordpress.org/plugins/
About Custom Post Types: https://developer.wordpress.org/plugins/post-types/registering-custom-post-types/
About the backup: it's super easy and you can even make a full backup using free plugins via back-end. But if the site goes down you can easily do it via FTP downloading only wp-content folder and the database. It's really simple to migrate from one WordPress to another, or from host to host.
About the hosting, you'll need to use a server if you want to build this project. There's a difference between wordpress.com and wordpress.org
The .com is simpler, you are not able to build everything you want. The .org is the open source project, which you get the files, upload to your server and connect to database (MariaDB or MySQL). Most hosts offer automatic installation for WordPress and, from there, you can change whatever you want and need.
Note: many developers create CPTs INSIDE the theme's code, but this is not recommended by WP as you can see in We recommend that you put custom post types in a plugin rather than a theme. This ensures that user content remains portable even if they change their theme.
WP is not really hard, after 1 week studying you'll see yourself getting over most difficulties. Even if it takes longer, don't give up. There's a huge community to help you with WP questions.
Hope it helps and I'm sorry my bad writing, I'm not an english native speaker.
C ya
I would like to integrate a remotely hosted blog into an existing ASP.net website.
I am not looking to host the blog platform itself because I would like to have a low friction solution where the users only have to concentrate on posting content and not maintain the blog engine. (So I do not want to build a workpress, dasBlog, etc. blog engine on my servers.)
The old Blogger FTP solution is kind of what I am after. What is the best way to accomplish this today?
My criteria:
- blog content is updated by users on a remote service (like blogger, etc.)
- blog content is displayed on my asp.net website with my website's look/feel/skin.
Thanks!
I'm actually in the middle of doing the same thing right now. The solution I came up with was to use the Application Request Routing and URL Rewrite modules in IIS7. You can get started here, but there's a couple more things that you'll have to do to get everything working. If you're integrating the blog into an existing site you won't want your rewrite rules to apply sitewide, so surround your ruleset with the element in the web.config and set it according to where you want the blog to appear on your site. Another thing that isn't addressed in Carlos's post is what to do about links that are referenced in CSS or javascript files, as they will not be rewritten. For those you will need an extra inbound rule that will pick up all of the relative urls that the first rewrite rule didn't get. You can look at the ruleset that I'm using (and maybe answer my question) here.
Hope this helps.
I want to move a drupal site to another domain and am looking for best practices, gotchas, hint, tips, etc to make sure I get through it smoothly.
Links and comments are appreciated.
You might want to give a try to the Backup And Migrate module.
There is also this handbook page that gives instructions on how to backup your drupal site.
It took me 1-2 hours. I do not have a step-by-step guide (I wish I had written everything down), but it entails updating the configuration files, updating the database (some tables have domain references, but I don't recall which - it could be that this was just for my image references in the Gallery2 database), and doing a cursory search of the content for full domain references in anchor links.
I migrated a Drupal 6 site with about 40 plug-ins, including Gallery2 and Google Maps integration, and I did not run into any major road blocks.
If you (and the authors of the contrib modules you used) did a good job by not putting absolute URL's in the code, it should be dead easy (I do it routinely when migrating the development site to a live production one, for its launch).
Of course I assume that you are doing things sensibly, and for example are not migrating a site from an apache/mySQL server to a nginx/postgres one, maybe also adding the need to prefix your DB tables in the process.
If this is the case, then you simply have to copy your entire file tree and export/reimport your DB.
If you are migrating between two similar architectures then chances are you will only have to change a few things in the settings.php file. The file is well documented. The only two things that I normally have to change are:
DB user/pass
cookies domain
In the file there are also additional configuration options like the possibility to choose the base URL manually in case of problems.
Don't forget to flush the cache once you log in the new migrated site for the first time.
EDIT: Just came to my mind: if you use any, you will also have to update your developer keys to third party API's (for example if you use google maps or google analytics) as these are domain specific.
HTH!
Basically, what mac said (+1)
In addition, I often need to adjust the .htaccess files a bit concerning the rewrite rules. For smaller sites on shared hosting environments, I usually place the drupal installations in subfolders within the document root (e.g. to allow for staging, etc.), 'hiding' the subfolder via URL rewriting. So for every 'move' of a site, I need to fix those rules.
The biggest culprit for me are sites that use modules that have to store absolute URLs in order to do their job (e.g. securepages). For those you should disable them prior to moving the site, adjusting their settings before reenabling.
If you are not sure if some of the modules you use store absolute URLs, it might pay of to extract your database dump locally and search the resulting file for occurrences of 'http://', 'https://' and the likes, as well as for your 'old' domain name (you'll need to exclude the watchdog and cache tables for this).