I'm fairly new to TYPO3 and as far as I can see it's pretty poorly maintained as far as documentation goes. Some of the tutorials and documentation are almost a decade old and I was wondering if anyone here knows of any useful extensions that could enhance the standard content tables in the backend.
I have some tables that contain a bunch of links with images. A sort of categories gallery with thumbnails if you will.
The point being that at some point this gets passed on to a client who won't know what to do with HTML markup and i was wondering if anyone knew of 1) a good WYSIWYG table editor extension and 2) a categories gallery plugin with the option to add thumbnails to each category.
Cheers.
Look for some of the more recent plugins. I don't usually go back more than a year or two when searching for an extension.
I'm not exactly sure what you're looking to do, but did you know you can arrange the standard image elements in different ways, linking each image to a different page, kind of like what can be seen at: http://www.thedemo.ca/demonstrations/image-and-text-alignment.html
Simon
Related
For the construction of an extensive list of links, since the source page is a thematic portal, I am looking for a suitable EXT., Which also runs under TYPO3 7.6 LTS.
it if the list of links to a permits the use of categories and multiple categorization of links is possible would be nice. should Weiterrhin the links are described not only the destination address and an alias but here should still an outline of the target page (possibly with photo) be possible.
Additional functions such as proposing links by users, reporting broken links or even a User Voting would nice additional features.
There were times the Modern Linklist, but they were no longer being developed for TYPO3 <6.x.
Is there perhaps somewhere an alternative or as one might like to vorhnandenen solutions might realize? It would be nice of course, without any programming knowledge, since I'm not a programmer.
P.S .: It is not about building a spam list but high quality links with topics relating to the original page.
As this seems to be a straight forward usage you could try to build that extension by yourself with the ExtensionBuilder.
just build up the records neccessary for your data. and let the EB generate all usefull actions: list & show, even create, edit, delete in FE would be possible.
Afterwards you just need to edit the generated fluid templates.
these links may help:
Overview
EB manual
small remark: if you want the newest code state, use the EB from git instead of TER
I`m not aware of an existing extension for it but it could be a good project to learn extbase / fluid.
You should also take a look at
typo3/sysext/fluid_styled_content/Resources/Private/Partials/Menu
and
typo3/sysext/fluid_styled_content/Classes/ViewHelpers/Menu
Fluid Content contains everything you need to create a list like that, you "just" have to combine the necessary bits and pieces.
You can do a lot with TYPO3 core functionality: there is a page type "external URL", pages can have categories by default, there are plenty of menu options (TypoScript HMENU, menu content elements, Fluid menu Viewhelpers). The Linkvalidator can periodically check all links and report broken links.
For suggestions you could add a form. Powermail for example can also store submitted info in database records, so your visitors could prepare page records (they are hidden until you make them visible).
we're just completing a new site build. With the current theme, we have had issues with structured data (we've highlighted it on Webmasters tools, and weeks later had to re-highlight it, and even then the highlighting prediction is not where we would like it to be).
It seems like Google is not able to find our Title, author, categories, content, featured image, date very easily. I'd expect to be able to communicate this to Google with 100% accuracy, since its so simple and we use the same format for all our articles). So maybe our theme is missing something by way of tags or something in the code to point to and identify this data?
Is that the case? Could someone please tell me what this aspect is called (so I can research it by its term), explain what I need to do with the new build, point me in the direction of an authoritative explanation/tutorial?
The site in question is a WordPress site, but I also am working on some php sites and would like to use this information on all sites, if it can be applied this way.
Thanks
You can use micro-data to mark-up the structured data. Also Google will really like your site if you show him (with a code) everything about the site - navigation, sidebar (aside), content (article) and so on. I suggest you to read about schema.org and micro-formats.
Here is an usefull article about your problem and how to implement micro-formats to your site.
This is not a direct code question, however, I think it may be useful. After google-ing for a while, I can't find a definitive answer....
A while back, I built a rudimentary CMS for shcool. Image upload, gallery, text, a basic captcha, etc. Basically a blog that you could upload images to. My quesiton is this:
Could any of you clever ducks tell me what features a robust, solid, home-made CMS should contain? I don't want to make a super fancy pants sort of site, but I do want to flesh it out a little. My current job is in Sharepoint design, and I don't want to lose any of the PHP skills that course taught me.
Any input would be greatly appreciated.
Thanks.
Well.. The best product is a product that reaches the requirements of the customer.
But I would say:
Dynamic menu
Dynamic pages
Different type of pages - front page, posts, lists, media, gallery
Secure back end
Dynamic user configuration
A install script
Template editor, where you can define modules
Maybe a offline post editor, with a up-loader (Drag a .doc file in a folder, and the file is automatically added as a post on the page)
I am building a fairly simple website based on typo3. I'm new to the CMS but I've read almost everything I could find about it - tutorials, wikis, documentation. I'm stuck with designing a functionality for the administrator to be able to create records with predefined attributes (category, date, info, image, ...) and those records to be listed in a table on the front end with a "View detailed" link on each row. Will I need to develop a complete extension for this? From where the administrator will enter these records? How can I iterate them on the front end?
I apologize in advance if my question is too broad.
The Kickstarter extension provides a full stop solution for your needs. There is a good set of, if slightly outdated, screencasts explaining how to use this extension to create your custom record types and associated front-end views.
I just started learning HTML and CSS, with no knowledge on other languages such as javascript, Php, and so forth. Websites like Refdesk.com boast fresh content everyday, there has to be someway they are able to have new content everyday other then changing it by hand. Some Google searches came up with nothing but RSS feeds.
How is this done?
Thanks for the helpful answers, it answers half of my question, but does this also mean that the owner would have to manually add the webpage each day for new content, or say add in the content for a few days and have them displayed day after day automatically?
Most dynamic websites derive their page content from a database. Change the content in the database, and the content on the pages changes to follow suit.
Likely they have some form of content management system which allows non-technical users to update the site. In some systems, the content manager itself can get quite advanced. Here's a description of the latest version of the one used at the BBC, CPS, which drives the many BBC websites and more.
They most probably use a database where they store the content and the newest entries are retrieved from this database and displayed. This requires a server side language like PHP, Java, Python.
The HTML is generated dynamically.
The answers about databases combined with a server-side language like PHP are pretty good and very direct, but depending on how new you are to web development they might not be conceptual enough.
The first thing you need to understand is that a database is a collection of tables - each like any you might be familiar with in excel.
For example, one table in your database might be named "daily_links" and it might have two columns, one named "Date", and one named "Link". So every time you want to publish a new link, you just make a new row.
So now you are half way there.
Now what the server-side scripting language is able to do is to go to the database, look at your table "daily_links" and bring back each all the information that it found there.
From there it can do anything with that information like make a new anchor tag in html for each row it found, and give it an href of the data found in the column "Link".
That is rough idea in (very) general terms.
I hope that is easy to understand.