Moving Joomla Images

Although there are a variety of ways to upload images to the Joomla backend, and there are system tools to move (mv command) files in a Linux filesystem, it is not always easy to clean up after yourself if you drop an image into the wrong folder.

Right now, working in the Joomla Admin I have had about 3 ways to get to and add "my media"

  • Joomla Media Manager  (under content- media)
  • JCE Editor (under componenets - jce editor -  control panel - file browser)
  • JSN PowerAdmin  (not seeing an interface just now - possibly in their Pro version)
  • ARK Media Editor ( Took a while to install.  - perhaps connected to Ark Editor.  No file moving appears possible -  perhaps is in their Pro version)

None of those, at my last view, would allow me to move a file.  All I couild do is upload a new one and delete an old one.  Technically, that is probably what happens inside a Linux Move command, but in an ideal situation, moving an image should also move the links to that image as well.

Today I started working with Balbooa Joomla Gallery and viola, it is easy to move images.  I expect it will also be easy to move and work with Galleries (which my sites absolutely need some work on just now).  

Best to Access via:  Components - Gallery 

Either Create a New Category or Edit one you have Created  (you can not do this from "Root" nor "All if you have no Categories.

Once you are "in a category" you can then access the Balboa Media Manager - easiest to choose Upload from Folder and start using the ability to manage your files more fluidly.

Granted, it would be nice if this were a bit easier and more intuitive to get to, but once you are there it works well

On the Gallery side it is nice that they build a "shortcode" to put Galleries right into Joomla content - and I could add some here if I actually had made a gallery by now.

The goal with this is to work efficiently and also correctly..  Joomla has some great aspects to it and it is quite extensible, but a considerable amount of time is required in researching, testing, and deciding what you want to work with and how.  If all goes well, this one will be a winner.  Excited for that, and kudo's at first round to Balbooa though certainly it would be nice to have a shortcut to their Media Manager.

I am certain that there are other ways to do this, but more time for aforementioned - researching, testing and deciding will be required.  I can envision a Dropbox connection at least for a raw image organization and feed.  Also a "double check" database to see what images are built in to content and that no damage is done with further massaging of the directory structure.

In the end, efficiency comes from smooth categorization and navigation on both the backend and the frontend.

 

Print Email

Wildnet Blog Accordion

Our service of installing TurnkeyLinux Builds on Linode Cloud - available now

Our service of installing TurnkeyLinux Builds on Linode Cloud - available now

I am pleased to announce the ability and availability to install for customers the latest TurnkeyLinux builds to the Linode cloud as well as custom modifications.

We have worked with TurnkeyLinux web applications for many years and are familiar with their value and flexibility.  Out of the box from TKL (TurnkkeyLinux) can be aquired via ISO and several versions of Virtual Machine as well as the Amazon Cloud install which TurnkeyLinux makes possible.

I have worked with nearly all of these variations and they do work well.  Still,  some 5 years ago now, I found that bringing the builds into the Linode Cloud envirionment gave me much greater possibilities from several points. 

Linode exceeds in value (bang for the buck) that is in Server Performance for the cost.  It also works very well in terms of being in control and able to scale on demand, either up or down, resources that are required..   It is possible to access via a range of ways, do migrations, modifications.   

TurnkeyLinux builds in the Linode Sphere are all the more valuable.  TKL has a great range of backup and migration capabilities, as does Linode, and they can work together.  Moreover, because the TKL platform is generally platform agnostic, it is also possible to migrate away from Linode with ease should you decide to go to a different platform, host your own, or simply stash away an archive of your system.  

Please read further or Contact Landis Arnold for more information

Read more

Using Git and TKLDEV to build your own customized Turnkeylinux (etc) resource set

Using Git and TKLDEV to build your own customized Turnkeylinux (etc) resource set

Learning anything takes some practice.  I have been hoverting around my reentry for a bit now and went in for a landing.  I am going to do my best to build a customized set of builds based upon the Turnkeylinux set of apps, but one which is more flexible and more customizable to my own needs.

Here are some of my process notes.  It seems to be going pretty well.

  1. Sign on to hub.turnkeylinux.com
    1. Set up a Micro Server via the hub to run TKLDEV
  2. Sign on to Github
    1. Go to your https://github.com/turnkeylinux-apps
      1. Choose the Core App
        1. Fork it into your own repository set (this will be suggested by Github)
      2. Choose the TKLDEV App
        1. Fork it into your repository set
      3. Choose someother App you want to work with  (I will do Joomla and Odoo for now)
        1. Fork it (or them separately) into your repository set.
    2. Go to your Repository Root
      1. For each new repository
        1. Make a new "Branch" with some operative name for your work
        2. Option - but recomended
          1. Make the new branch be the "default" branch for you (rather than "master" being default)
  3. Log into your TKLDEV Box via SSH - ie Putty.  Iin my case the TKLDEV generated on hub.turnkeylinux.com)
    1. cd /  (out of /root)
    2. cd turnkey  (1 and 2 together could be "cd /turnkey")
    3. cd products (1 and 2 and 3 together could be "cd /turnkey/products")
    4. Clone each of your repositories (using the -b default_branch_name) to your products directory using a command like the following
      1. git clone https://github.com/your-user-name/your-turnkeyapp-repository -b default_branch_name
      2. cd (from products) to one of the new cloned directories
      3. issue the "make" command
    5. If you want to remove and start over I use the following
      1. rm -rf directory_name
      2. I may have to "restart" the server if I cannot complete because some chroot is running after a "make command"..  After reboot again use the rm -rf directory_name command to clear it.
  4. I am right there now.  I will start working with Git on my personal branches and see what modifications I can run
  5. My specific focus will be on TKLDEV modifications.  
  6. If I want to use those modifications actually "inside" my operating TKLDEV appliance  I will likley need to Link the Code directly - which means this is a Line of my TODO list.
  • Now to BuildTasks
  • Forked https://github.com/turnkeylinux/buildtasks into my repository set -ie https://github.com/my-user-name
    • Created a Branch - my name
    • Made the Branch "Default"
  • Opened GitHub Desktop
  • Cloned https://github.com/my-user-name/buildtasks into my GitHub Desktop
    • copied bt-xen into bt-mine
    • copied /patch/xen/ into /patch/mine  (min is a pseudonym)
    • Made a Commit with Summary and Detail Annotation
    • Pushed the Commit with Summary and Detail Annotation
  • Opened my TKLDEV Machine with PUTTY (SSH)
    • Navigate with
      • cd /turnkey
    • dir (to be sure)
    • rm -rf buildtasks
      • that removed the buildtasks directory so that I can clone my repository
    • git clone https://github.com/my-user-name/buildtasks -b my-branch-name
      • technically the branch part should be covered automatically as I set it as default in github directly, but I try to be safe and specify the branches explicity.

That takes me to where I am now.

I need to start working on my Build Processes next.  Also, quite explicitly, I will need to overtly change the "include" command for buildtasks if I go to make new TKLDEV systems that use my buildtasks.  However, it seems easy enough just to change it manually as I have  just done to my working TKLDEV server.

  • 3 Changes made in Buildtasks (XEN) directory
  • Committed Changes
  • Pushed Changes
  • Went to Putty:  Git Pull  (3 Changes Made)

Lets Test a build

UPDATE:  10/23/2019

The Build process worked well.  I then had to wrangle (again) with network settings inside of my Server Build, but those were not related specifically to the TKLDEV process.

From here I will move the changes I made into my own BT-process and see if I can replicate my results and also get the few more tweaks for my server build integrated as well.

I need to understand a-bit about the Patching process and how it applies to files outside of build tasks  (ie, small changes to the Core build).  I also will need to test various updates from REPOS and TKLBAM to see that I can have my changes from TKLDEV stick.

All for Now.  Very excited about the project.

(Postscript)

To build in XEN, ie (check /mnt/isos for valid build names after)

./bt-iso appname-x.x-stretch-amd64

followed by

./bt-xen appname-x.x-stretch-amd64

Read more

MageBridge removed as well

MageBridge removed as well

Looking back at my notes, I started working with Magebridge (from Yireo) in at least 2013 and perhaps earlier.

It was a great idea fraught with difficulties.  Its purpose was to bridge Magento into Joomla

Magebridge discontinued by Yireo a few years ago now, but on my side I just disabled it.  Yireo discontinued because of the forthcoming Magento 2 and all the changes there.  I am not convinced it could not have been brought forward, but I think the greater issue was the extreme complication the program was itself.

Today, I gave it one last try.  Nope...  no go.  And now I am free.

Everything has been removed (uninstalled yes) including Compnents, Plugins, Packages, Libraries, Menu Items, Modules etc etc etc.  As the attempt also disabled the Magento server I also have a full restore running there as well (to last night's state).  I will likely kill the Magento server next.  Also not worth the hassle.

The site is fast.  I did resurrect for the time being Dynamic404 from Yireo (Yireo has gone away from all things Joomla).  It seems to have some good rerouting and be able to redirect what it cannot find in the overt redirection tables (lets see how that goes).

This is not, of course, big news, but it is news about Old and New.  I have long wanted everything to stay functioning, but sometimes we have to clear the decks...  They are clear now and we won't try that again.  (I log that I spent almost 4 hours on this attempt this morning).

And so it goes.

Read more

Magento Sunset

Magento Sunset

I have been running Magento since about 2012 with 1.3x in my memory bank. Up to 1.9x now and really just using Magento as a repository now.

Magento 2.x (2.3x to be precise) is here.  It does not work, at present, with this CMS system so I have a linkage taking place through Filemaker from J2Store to Magento and by extension to Odoo.

I will quite likely just take the Magento system down.  It will not be supported with updates after this coming June and the time investment of getting 2.x running and keeping it running does not seem available just now).  We will see.

Anyway, for now, I am going to start redirecting the URL's to land into this system.  Lets see what a pain that becomes.  Likely worth the effort but also perhaps now.

Sad, but Magento was aquired by Adobe and like Odoo, they are making it more and more difficult to use it as a Open Source software.  Not that either are impossible, but the reigns are steering the team towards privation.

Somewhat the nature of things these days I will say.

All good software, just a bit too time intensive.

Read more

Magento - Odoo - OCA Connector

Magento - Odoo - OCA Connector

This is a very functional system which brings the ability to work the "backend" of Magento by actually building and purchasing items you sell,

  • Functionally you get all of the aspects of Odoo, including CRM, Product Management and more
  • You also get the great E-Commerce capabilities of Magento, and its increditble extensability.

(to do:  more detail)

Read more

Joomla3 Appliance - Powered by TurnKey Linux