giollianosulit

Hi there,

There are multitudes of ways to go about this.
Using Dreamweaver + MAMP is quite an odd combination (coming from 5+ years of commercial dev experience) and not recommended.
But if you’re going to go this way here is my advice.

Your biggest problem here will be keeping the WordPress Install + Theme in seperate repositories.

So you will need a repository for your WordPress Install + Plugins.

Have another repository for just the theme that you upload to the WordPress install (don’t worry about merging the two repositories together, keep them seperate to keep it simple).

This does mean you’ll have two repositories, but any WordPress updates / Plugin updates you can easily track and push to your live site without polluting commit history with your theme updates (and also dealing with a whole lot of merges).

If you’re dead set on using MAMP, the best to do this will be to:

1. Checkout the WordPress Repository you have made into MAMP/htdocs
2. Add a gitignore entry for wordpress-install/wp-content/themes/*your-theme*
3. Checkout your WordPress theme you’ve just made (NOT in MAMP/htdocs, can be anywhere else on your computer)
4. Set the repository you’ve just checked out to sync to MAMP/htdocs/wordpress-install/wp-content/themes/ when you save a file (initially you want to sync all the files into the theme) – *Note* Not sure if Dreamweaver can do this. I know in Sublime-Text you can use FileSync Plugin.

Doing it this way will keep things very simple, in my opinion if you plan on doing it the way you mentioned above the git branches / commits will get very messy, very quickly.

Then when it comes to push changes to your live website you you can sync across whatever is in MAMP/htdocs/wordpress to your server.

*Note* Having everything in one repository will allow you to use git post receive hooks to automate deployment. The advice above is just to get you started in an easy way that will keep your life simple and help you understand the process.

• This reply was modified 7 years, 4 months ago by giollianosulit.

It looks like this question has been answered before a few times on stackoverflow, but essentially:

The get_post_permalink() funciton fetches the link to a post depending on its “permanent” link plus your custom rewrite rules that changes ?p=123 into for e.g. my-beautiful-sunday-diary. The get_permalink() function is more “basic” but as well more versatile in what it does.

Source

• This reply was modified 7 years, 4 months ago by giollianosulit.

Hi there,

The solution to your problem looks pretty simple.

wp_enqueue_style(‘child-style’, get_stylesheet_directory_uri() . ‘/style.css’, array( $parent_style ), wp_get_theme()->get(‘Version’));

Should Be

wp_enqueue_style(‘precies’, get_stylesheet_directory_uri() . ‘/style.css’, array( $parent_style ), wp_get_theme()->get(‘Version’));

I can see you’ve used the WordPress documentation to copy that function to add a child CSS file to your child theme, but you didn’t actually put your theme name into the wp_enqueue_style.

Fairly simple mistake to make, to help in the future I’d suggest reading up on https://www.php-fig.org/psr/ to get an idea of PHP coding / styling standards as the way some of your code is formatted (maybe the WYSIWYG just didn’t carry over formatting) makes it unnecessarily hard to read.

• This reply was modified 7 years, 4 months ago by giollianosulit.
• This reply was modified 7 years, 4 months ago by giollianosulit.

Um linux has a completely different directory structure compared to Windows.

Depending on what variant of Linux you’re installing it on, your files should go into /var/www

This is most likely due to your .htaccess file not being copied correctly.

Did it come across during the migration ?

So have you got access to the database of the website ?

That may be your only option if you’re sure you haven’t registered that email

A subdomain will do the trick. Just install the files in a directory inside the existing website. Than just move them out once you’re ready

The twenty twelve theme is responsive, are you installing it on top of an existing theme ?
It may just not be activating correctly or you have other plugins interfering

Yeah those instructions on that first link you were following are somewhat lacking.

But really you’d want to:

1. Copy all the WordPress files to the new location
2. Dump the Database into an SQL file
3. Re-import that database into the new location
4. Update your wp-config.php connection settings to the newly imported database
5. Under the wp_options table in your database, change any reference to the existing domain to the new one. (Should only be 2)

It looks like you’re wp-config file has been modified somehow / some files deleted.

Made any recent changes to the site ?

If you haven’t, your server may have been compromised.

Good to hear it’s fixed, sometimes w3 Total Cache can be funny.

If you’ve decided to uninstall it and it’s still playing up (you’re old style is still showing) it will be because W3 Total Cache leaves cached template files behind that hold the existing layout

What @catacaustic said is very true. Your site will be treated as ‘spamming content’ since you’ve duplicated it multiple times.

Is there a reason for needing to duplicate the site in different themes?

You should check what the memory limit on your server is set to.

This usually means you’ve used up all your RAM.

@respectyoda, yep integrating HTML5 into sites is the way to go, however based on how they’ve asked the question, the stuff from H5P seems very complicated!

A plugin you could install into WordPress seems like the easiest solution, if they choose to go that way

Are you pointing your sites DNS to cloudfare ? If you turn cloudfare off then yeah it won’t work.