I'm new to sitecore have been tasked with creating some ppc landing pages for a client who's developer has moved on.
Their previous developer had created several of these pages in the past and the content is very similar so I have copied one of the previous pages and changed the content.
The problem is that the copy is still referencing the content of the original page, i know this as if i change the content of the original the copy also changes too.
The pages sub items are a mix of rich text fields and custom sublayouts.
Have I done something wrong or is this a bug? Can anyone suggest a fix?
Id imagine something like the reference to the subitems in the database has not changed from original.
How did you copy the previous page? In Sitecore you should be able to use either the Copy or Duplicate command, and be able to change the copied item without the original being changed (our content editors have a habit of doing this as well).
My guess would be that the sublayouts are pointing at a specific item, rather than the Context item, but that would be hard to say without code or ascx snippets.
Related
I should create a moodle wiki and I have got some sections on my wiki-page. Now I would like to create a table of contents where The user can jump between the sections like on Wikipedia.
What I tried:
section1
...
<h2 id="section1">Section1</h2>
The problem I got is that when I save the page the id property will be removed from the tags
If you are using one of the latest version of Moodle, it is possible to make the HTML ids stick if you add you HTML markups within the Wiki HTML editor.
This has to be the ultimate change you do to the document. Once you have your HTML correctly tagged, directly hit the Save button without going back to the editor's preview mode. They should be available in the Wiki after that.
If you need to edit the page again, be sure to keep a local copy of your HTML structure, in order to avoid having to add the HTML markups again. They will be removed everytime you edit the page or if you switch from the HTML editor to the WYSIWYG preview mode.
I'm planning to try using dokuwiki to manage my large collection of notes, and one of the major attractions is its flat file basis that'll allow me to edit via scripts etc. I had a question - suppose a page's material fits into multiple namespaces. If I were to create the file in one namespace and then create symlinks in the other namespace directories, would that work? Or would that screw up revisions etc?
Yes, you can do that. But yes, this will mess with your revisions a bit:
when DokuWiki saves a page, it copies the data of the old page to the attic
the name of the attic file is the same as the page that was edited, but with a timestamp appended
because new attic files are created you can't work with symlinks in the attic
Imagine you have the following setup:
data/pages/original.txt
data/pages/copy.txt -> original.txt
You now can edit the pages original and copy in your wiki and they will both always be the same. However old revisions of the pages will be split between the two, depending on which page you edited.
Instead of messing with file level consider
Include plugin to share content between pages.
Creation of some 'commons' namespace for such pages to be DRY.
Namespace templates (+ additional plugin).
Pulling content from page side instead of pushing it to pages. This might be good to start with. You can always include some php code or even write your own plugin.
How to change the Moodle logo which will be displayed at the footer page and change to some other logo? As per the given link 1 I have tried but I could not find the footer.html file in my themes folder.
So please help me with some other method (which does not use local machine because I'm working with a remote machine where I could access only the Moodle site, and nothing more than that) to change the logo and link of Moodle.
This depends on your theme - So you're not going to get a precise answer unless you post more details. But here's the gist:
Every theme is made in parts. Normally, you have a header, a content, a sidebar (or two) and a footer.
You want to be editing the footer file.
The footer file is going to be something within the lines of footer.html or footer.php... Something like that. Again, every theme is different so it could be called something completely different. Sometimes, you just need to dig around.
Please also consider that your footer file may also be contained in a sub-directory in your theme folder. So make sure you have a proper look before deciding to "call off the search".
Anyway, once you've found your footer file (Whatever it's called), you'll want to open it and find the image.
If the image is inserted as a HTML reference of location, you can find it by Ctrl+F and typing in the name of the image file. E.g. "footer.jpeg" or whatever.
If the image is inserted as a PHP relative reference, e.g. "$FooterImage" then don't change that, instead, find out where the variable is pointing to in terms of the file-path, and go and edit that image file via FTP instead. You don't have to keep the PHP variable, but I'd keep it in for code-integrity purposes.
Tip for the future: Please include information like name of theme and Moodle version. It enables us to help you better.
Clean Theme:
Things are a bit different with Clean Theme as it doesn't have a single footer file.
You need to go into all layout files one at a time.
Look for this div:
<footer id="page-footer">
...
</footer>
In this footer, you will find a PHP command that says:
echo $OUTPUT->home_link();
To remove the logo, remove this line.
To replace the logo, you can either:
Replace the "home_link" reference in PHP to point to the new image file.
Or
Remove the PHP line and replace it with
?><img src="link_to_your_image" alt="Logo"><?PHP
Remember, you will need to do this for all layout files.
Have a look at Footer replacement at the official Moodle Documentation. Hope that helps.
I would like to be able to use "manage content and structure" to move sub-sites within a site collection (SharePoint 2010). For example I have a site that is right under my top level site and I would like to move it to be the child site of one of its' current peers.
There is some concern from admins that this creates a mess in the content DB, therefore all moves should be done using powershell export/import.
Can anyone tell me, technically, what happens when we use the move command in "content and structure" within a site collection and if there are known issues with it?
Moving sub sites around within a site collection is no problem. They had the exact same command for moving sites in SharePoint 2007, and it worked.
When you click the button, what likely happens is there is a stored procedure that executes and moves all the data to the new location.
Databases are designed to handle the all these changes. You don't create more of a "mess" in the content database by moving a site around compared to the daily "mess" of adding new documents to document libraries all over the place. In fact doing a PowerShell export, delete old site, import process is probably more messy because the old site isn't 'deleted' it's moved to the "Recycle Bin". And some of the GUID's associated with the site will be changed on the import.
Basically my recommendation is use the Move command to move sites around as that's the easiest thing to do, and don't worry about the database, because it just works.
I need to add some text to this file [template/payment/form/purchaseorder.phtml], for a particular store within clients' magento site. When I make a change to the purchaseorder.phtml file, it changes the text on all the stores. So I need to somehow customize this for one store in particular.
I have read comments on several sites, some mention changing the local.xml, change the config.xml, make changes in admin panel, but this such a small change, I don't want to disrupt anything by going overboard.
I need to extend the functionality on the backend so this change can be made for a particular store or stores. the sites has five stores built into the one install and for now I need to make the above change to just one store.
I think I need to somehow add a PO field Heading and an "Additional Text" option to the Purchase order section in image two. is this correct, if so how do I do this?
Could someone point me in the right direction to making this type of change please.
Note: I can't do the create directory structure, copy files, change needed files option
This is magento 1.7
Copy purchaseorder.phtml file from base/default directory then paste it in your current template. Now you can alter content of it purchaseorder.phtml in your current directory, it wont affect the base file.Like below,
Copy from
app/design/frontend/base/default/template/payment/form/purchaseorder.phtml
Paste to
app/design/frontend/base/current_theme/template/payment/form/purchaseorder.phtml
When you override a section, the folder structure should resemble the default template folder structure like current_theme/template/form/ payment/purchaseorder.phtml .
sorry for bad english.