Drupal Content changes to Plain text on Cron run - drupal

I add content to an article (either administrator or as content user) and I save the changes as Full HTML or Filtered HTML.
Once I run CRON,the article is marked updated and when I preview it i see plain text instead of HTML.Some sort of over writing is taking place which I am unable to figure out.Earlier I thought it was a problem with the webform module but it is not.I tried disabling the modules one by one but was not able to detect the problem.

Do you check your content under the same user ? I can hardly believe it's a time related issue. It seems more like a rights problem. Do all the relevant roles have access to the input filter Full HTML ?

Related

Drupal - Newbie - Need some help in finding content

It seems a very simple job but really been tough to perform.
All i need is to edit a content but i cannot find it inside the cms which says "Commerce Kickstart"
The page address of the content is like this:
https://website.com/abc/def-ghi
When i select Content>Manage Content from the top header bar (after logging in as admin the top bar appears) then it shows lots of pages to edit but i couldn't find that particular text inside any of them.
So i decided to download the mysql db and search for the text using notepad++ but i found several instances and i guess its all from some cache table.
I put so many hours on finding this easiest task but failed.
Any advices?
Thanks!
Do the pages have content within them?
When you are on the Content Overview page just click on edit and see if there is anything in them.
From what I can infer you are using Commerce Kickstart and this probably implies that you might need to edit the product instead. Just answering from the top of my head.

New UI SiteEdit Implementation

I have implemented New UI SiteEdit in Tridion 2011 SP1. When I have created a page without components in it ,I am able to edit the page. If I am inserting the component I am not able to edit the page. Please help on this issue?
When changing a Page in New UI (Experience Manager or XPM), the page is checked-out. What you might be seeing for other users is expected behavior--other users should not be able to edit the page in the CME or within XPM.
Also, you should be restricted from editing content page for even the same user that has a different session (e.g. viewing the page from another browser).
When editing the page with the same user and session, you should be able to add multiple components. The page is checked out. Editing content on the page should be "editing components," rather than the page itself.
Let us know if you're seeing something else.
This can be a result of having an syntax error in your inline editing commands (i.e. the JSON syntax inside HTML comments). Normally you would use the OOTB building blocks that generate this for you, however, in some extreme scenarios, this syntax is written out by hand. I suspect that you may have the latter scenario. Verify your component and component field command syntax.

HTML formatting error on Umbraco workflow notification emails

I've posted this in the Our Umbraco forum (http://our.umbraco.org/forum/ourumb-dev-forum/bugs/30914-HTML-formatting-error-on-workflow-notification-emails) but would like to expand the audience as I need a quick resolution to this problem.
There appears to be an issue with the HTML used in workflow notification emails, property names are displayed but their values are not visible. The HTML content is there and if I save the source as an .htm file and view it in Firefox the values are displayed (although in the wrong location).
The HTML is generated from the sendNotification function in the umbraco.cms.businesslogic.workflow namespace, I am using Umbraco v4.7.1.1 and this problem was noticed in Outlook 2007.
Has anybody else encountered this problem?
It appears that this issue has been logged with Umbraco (http://umbraco.codeplex.com/workitem/26577) but has not been addressed.
The fix is a simple code change, for my current project I have decided to download the CMS source code and make the change myself. This works but throws up maintenance issues e.g. ensuring my change is not wiped out during a CMS upgrade.

Can openx server just xml for a banner instead of adding html?

I want to set up a zone in openx which will be invoked from a flash application, so I want openx to just serve back whatever xml I paste into the 'generic html banner'. Problem is when I use the invocation code for the zone, openx is putting some html around the xml i specified.
Is there a way to get openx to return the xml without adding html around it?
Edit: The same problem occurs no matter what zone type you enter, openx wraps some extra text around it. It appears what I want to achieve cannot currently be done with openx.
After investigating, I have found there is no out of the box way to get openx to return the xml entered without modification.
It might be possible using xml-rpc. However, if this is not a viable option, then you can consider creating a clone of the ajs.php file to only throw out banner content.

Parsing PlainText Emails from HTML Content (ASP.NET)

Right, in short we basically already have a system in place where the HTML content for emails is generated. It's not perfect, but it works.
From this, we need to be able to derive a plaintext alternative for the email. I was thinking of instantly jumping on and creating a RegEx to strip the <*> tags from the message - but then I realised this would be no good because we do need some of the formatting information (paragraphs, line breaks, images etc).
NOTE: I am OK with actually sending the mail and setting up alternative views etc, this is only about getting plaintext from HTML.
So, I am pondering some ideas. Will post one as an answer to see what you guys think, but thought I would open it up to the floor. :)
If you need any more clarification then please shout.
Many thanks,
Rob
My Solution
OK, so here it is! I thought up a solution to my problem and it works like a charm!
Now, here are some of the goals I wanted to set out:
All the content for the emails should remain in the ASPX pages (as the HTML content currently does).
I didn't want the client code to do anything more other than say "SendMail("PageX.aspx")".
I didn't want to write too much code.
I wanted to keep the code as semantically correct as possible (no REALLY crazy-ass hacks!).
The Process
So, this is what I ended up doing:
Go to the master page for the email messages. Create an ASP.NET MultiView Control. This control would have two views - HTML and PlainText.
Within each view, I added content placeholders for the actual content.
I then grabbed all the existing ASPX code (such as header and footer) and stuck it in the HTML View. All of it, DocType and everything. This does cause VS to whinge a little bit. Ignore It.
I then of course added new content to the PlainText view to best replicate the HTML view in a PlainText environment.
I then added some code to the Master Page_Load, checking for the QueryString parameter "type" which could be either "html" or "text". It falls over to "text" if none present. Dependant on the value, it switches the view.
I then go to the content pages and add new placeholders for the PlainText equivalents and add text as required.
To make my life easier, I then overloaded my SendMail method to get the response for the required page, passing "type=html" and "type=text" and creating AlternateView's as appropriate.
In Summary
So, in short:
The Views seperate the actual "views" of the content (HTML and Text).
A master page auto switches the view based on a QueryString.
Content pages are responsible for how their views look.
Job done!
If any of this is unclear then please shout. I would like to create blog post on this at some point in more detail.
My Idea
Create a page based on the HTML content and traverse the control tree. You can then pick the text from the controls and handle different controls as required (e.g. use ALT text for images, "_____" for HR etc).
You could ensure the HTML mail is in XHTML format so you can parse it easily using the standard XML tools, then create your own DOM serialiser that outputs plain text. It'd still be a lot of work to cover general XHTML, but for a limited subset you plan to use in e-mail it could work.
Alternatively, if you don't mind shelling out to another program, you could just use the -dump switch to the lynx web browser.

Resources