I am publishing content on a TYPO3 instance where I have just editor rights. At the moment, that content is generated automatically as HTML; my workflow consists of
Copy HTML code
Log in to TYPO3
Select page
Click Edit on the HTML element of this page
Paste HTML code
Submit
Is there a library or an API that helps automating this process?
Since you are only an normal editor in your TYPO3 instance, I assume you cannot just add a TYPO3 extensions that helps you with the task. If you could alter the TYPO3 instance, there would be numerous ways to automate the process: A Scheduler task that fetches new content and puts it to a page or even fetches content from a mailbox or Dropbox share etc..
The only solution I see is that you do some browser automation to perform this task. You use e.g. use Chromium Browser Automation if you work with Chrome. You can record all form entries (username, password, paste text to RTE) and clicks and you also should be able to define some variables (ID of the page and content element, content itself).
Related
I want an spfx made webpart that I've made be able to send an email (I'm using IEmailProperties at the moment) which provides a link to a modal form?
For example:
User clicks button in webpart, form loads.
User fills out form and submits it to SP list.
Form sends email on submission. Email has a link to the actual item created, so when the user clicks the provided email link, it opens up the modal form.
I would presume that the user would HAVE to be sent to the SP page where the webpart is unconditionally, but would it be possible to open up the modal corresponding to the SP list item?
Is this feature available in SharePoint framework, because if it isn't, compared to something like InfoPath 2013 or PowerApps it's quite a limitation.
I've researched this with several shallow Google searches and on gitHub for any premade stuff, but alas there is nothing that I've spotted.
I've been told IT IS possible:
"Yeah, they’d have to visit the page. Email clients don’t do JavaScript so you can’t really do interactive stuff there. If you want to take them directly to a page that then displays a modal, that’s plenty possible though. (e.g. display the modal based on if the URL contains a certain string)"
But wouldn't know how to do the above, can anyone start me on the right path?
Regards,
T
In the email, pass a query string containing the item ID/list ID etc of the item, then have the webpart read the See: How can I get query string values in JavaScript? If your values exist. If they do exist, then open the modal using some kind of framework like bootstrap or fluent UI. You can write your own form using PnPjs or use an iframe potentially to display the OOTB edit form.
Additionally, you can link to any page in SharePoint provided you use an extension instead of a webpart to host the modal. You can install extensions tenant wide, and have it listen for the query string.
I am trying to create user rights in Typo3 7.6 so that a user can simply work as an editor. He has, for his department, a section of the page tree. In that he can almost exclusively create text & media. For a single subpage of this whole tree, it also requires the ability to create an HTML element.
From my personal logic, it would be sufficient to create a user group (A), with all the usual rights would be covered. So creating pages, texts and media. A second user group (B) then only with the explicit permission to create HTML elements. Under Access, I have selected the group in the entire page tree as a simple editor (A), under which one page may be on the HTML, but the second user group (B).
But now it seems that as soon as the user receives the group B, it is not only allowed to create HTML for the one page, but the entire page tree.
What am I doing wrong? How is that otherwise thought?
This doesn't work this way. The permissions of all groups are combined and are the same on any page.
A possible solution could be to use the extension content_defender and a different backend layout for those pages where the HTML element is allowed.
Just as a side note: Allowing an editor the HTML element is a security risk as the editor can also create JavaScript and with that can get admin permissions and other stuff. So I would be very careful with that and would avoid allowing this element for admins.
The Typo3 extension tt_news enables for example all created news by this extension to be shown in the newsletter but not content from a "not news" page of the website.
We are looking for a plugin which automatically finds new content on the website and let us create a newsletter from it.
What extension could be used here? Might direct mail be able to do so?
Taken from the Direct Mail manual: "Newsletter pages are just normal pages. Their rendering is configured by the TS template."
A very simple solution for what you want to do would be to write a simple extension where you get the newest content elements and output them. Direct Mail itself will not do that for you, but it will send out any content that you provide on the "Newsletter page".
I'm currently working on a website and I have to use Prestashop.
I created a back office interface that allows the user to write, edit and delete articles. So I put a tinyMCE editor in it.
The problem is that when I click on 'save' to store the article in the database, it only stores raw text, without the styling content (html tags, bold text etc)
I would like to know how to get the whole content, including html tags, styling etc.
Thank you.
Ok so all I had to do was to change self::TYPE_STRING to self::TYPE_HTML in my Article.php file.
I am using jeditable and had it working very weird.
after editing the editable field and submits it instead of printing the new content it displays the entire document window in the textbox(placeholder of editable content).
question: from the example where the author used save.php. what was the content of save.php?
is it necessary to send the result on a php file?? can't an HTML file work?
I believe within the comments box at the bottom of the author's main page - somebody has kindly provided a version of the save.php file for people to use and modify as needed.
The save.php file is used to actually save the values of the editable field/s. Without it, nothing would happen to the data and it would reset to the default text if the page is refreshed.
Options instead of a php file could be:
Saving the text/select changes to a Cookie
Using another server side methos such as asp, jsp, rails or .NET to process the saving of the changes.
an html page is a static page with no processing facility per say to communicate with the website server, so no.. html is not suitable for such a need.
Saving script must return the string you want to display on page after editing. You are now returning full html page.
Source of for all demofiles can be found from GitHub.