I have a problem to make Simple Image Gallery to work in Joomla 3. It doesn't display any pictures, actually it doesn't even care about them.
I have this pages:
http://utsnorthsath.kangoowebs.com/gallery/images/34-short-course-cross-country
It looks like {gallery} tag is not recognized/parse and no gallery is displayed. Does this module SIG require any additional action after installing to tell Joomla that {gallery} tag should be parsed now?
I don't get any error message, just the content is not parsed.
Thank you for any help.
Don't want to teach you to suck eggs but when I find {plugincodes} rendered as is, it either means you haven't used the syntax correctly or you haven't enabled the plugin in Plugin Manager.
One other thing which may be affecting the plugin is that you load jquery before Mootools.
Best practice is to load these the other way around.
You could look for an excellent plugin called JQuery Easy which should fix that issue and possibly the Gallery issue too, if the above isn't it.
Related
I am writing a Program in Rub On Rails 4.x and I have to take PDF files with defined fields that can be filled out, fill in data from a form submission(This part is DONE!), and lastly allow the user to modify the saved PDF file on the server and overwrite said PDF after making their modifications.
Like I said I have already gotten the PDF files filled out with what has been submitted in the form through pdftk . What I now need to do is provide a server side editing capability to the said PDF files on server generated from the first step of the process.
I have seen similar posts but none wanting to do the same thing I do. If I am wrong links would be great. Thanks in advance for all your help!
After lots of digging and research here is what I have found to be the facts surrounding this issue and implementing a program to allow embedding the PDF file, editing it, and saving it back to the server. This process would be great however from what I can tell there is nothing out there that really does this for Ruby On Rails. To quote #Nick Veys
Seems like you need to find a Javascript PDF editor you can load your PDF into, allow the user to modify it, and ultimately submit it back to the server. Seems like they exist, here's one for ASP projects
You are correct but still wrong in the sense that yes there is one for ASP projects however that is Microsoft Based, yes I know that it can run on Linux environments through Mono. However to the point it would appear in this instance that a Ruby On Rails specific solution is indeed needed.
The solution that we have come up with is as follows
1. Use a PDF editing package in the linux repositories like PDFtk
2. You then render a page with the PDF embeded on one side and a form representing the live fields in the PDF to take input.
3. Once submitted you use PDFtk to write the values into a new template PDF file and overwrite what was previously stored.
This requires a few additional steps to process the data than I really care for myself. However it is the best solution that our team could come up with, without bleeding the project budget dry for just 1 piece of functionality.
I hope this helps anyone else looking to do the same thing in Ruby On Rails.
I have done something like this using my company's .NET product. It can also be done using its Java version too.
http://www.gnostice.com/nl_article.asp?id=255&t=Save_Form_Submit_Data_Back_To_Original_PDF_Document_In_NET
Hi everyone I am trying use tinymce-rails and and also have an upload form. This works really well since I can call the images anywhere. Just about everything is working great. The images upload, the tinymce styles stuff.
Now the weird thing is tinymce keeps adjusting the file paths to add "../../../" and this breaks the photos when editing the text. It would actually work fine if it would just go up one more "../" count on the edit page, the pathing does work on the show page.
Does anyone have any direction they can give me?
As I can't know the source of this, I can provide a workaround.
In your model, let's call it Post, you might need to replace stuff to the field containing the html, let's call it body:
before_save {
body.gsub!(/(\.\.\/)+/,"..\/")
}
I'm having all kinds of trouble getting CKEditor working in a Rails app.
It always makes a request for skin.js which doesn't even exist in the stock package.
Whether or not it displays the groups I specify seems completely up to chance. Some of them work (like Clipboard), others don't (Like Document).
All the icons are messed up. They display on the wrong buttons. Sometimes the same icon will show up on two separate buttons.
I have no idea what's going on. I didn't customize anything. I got the 4.4.0 download straight from the homepage. Standard package.
Any thoughts???
Thanks!
This problem usually occurs when it clashes with any other js script in the project. try downloading the code and run it in a separate project, if it works fine there , this means you have some other js in your code conflicting with the ckeditor script and usually this is the inline js which causes problem.
I'd like my users to be able to upload an image by pasting it into a form.
Is this possible somehow with Rails?
I'd like to do this safely and limit to a single picture upload, not a completely open textarea.
UPDATE:
I'm looking for something like http://pasteboard.co/ that I can add into a form in a Rails app.
Also, with a paperclip hook like https://github.com/galetahub/ckeditor would be nice
Although I don't have a specific answer (copy & paste), I do have an answer regarding how to implement the uploading within the DOM:
JQuery
If you use something like jquery-file-upload, you'll be able to incorporate a GUI-based upload process to Rails
I think your question can be answered by taking this technology & applying to the specific element where you'd like to "copy & paste" the image
You can drag & drop images from your system into the example above. This is very similar to the copy & paste functionality you're seeking. I would personally look at this technology, and then apply it to the copy & paste procedure
WYSIWYG
You've referenced GMail as a great example of this -- but you have to remember they're allowing you to paste into a WYSIWYG editor
This is very important, as the upload image element will be handled through the WYSIWYG. You may be able to use this resource to help:
Wysiwyg with image copy/paste
My clients can enter text into textarea and have the option to use the markdown or textile filters for each textarea.
With some models (articles, newsletter, etc) they can upload images to associate with the model, which are displayed in a column next to the text of the text.
This worked fine for a while, but they have now told me that the want the ability to put the images INSIDE the text a specific positions.
What is the best way to go about this? I suppose I may have to use a wysiwyg for this, but would rather not. And how would this work for images which are not yet on the server, etc?
There are different directions you could go to:
Follow the path of Confluence, which released in their new version 4.0 a rewritten WYSIWYG editor, that stores as source XHTML, not any more wiki markup.
Leads to an update of all pages when migrating.
Was pretty difficult to implement. I do not know if they use any more the TinyMCE editor of previous versions.
Follow the format of markdown how to include images in your source format. So by typing: This is my text. !image.png! The inline image shows ..., you will have a format that is understandable.
You have to expand the interpretation, so that the !<filename>! will be mapped that is stored locally anyway.
You have to add clear-up dialogs for the images that are yet not known, so doing bulk uploads ...
You may provide a drag area on your view, that then shows the filename and gives examples how to include that inside the text area.
Go for something in between, by allowing users to drag images inside the editor. There are plugins written in Javascript that allow you to do that, e.g. UI Draggable for jquery
I have no idea how to integrate that image inside the text editor. Overlay?
So the second one is the easiest, and the user knows how to do it. If they only decide that this is the solution they want to have :-)
I think I'm going to use a combination of #2 above, and the Liquid templating engine.