I'm trying to access the Tags component manager (administrator/index.php?option=com_tags), but gives a 404 error (View not found [name, type, prefix]: tags, html, tagsView)
Tags is working ok, I can add a new on a article, but I can't manage.
Using Joomla 3.6.5 and tested using mod_rewrite on/off.
Is there any one experiencing this?
The tags extension is a protected extension, so technically it can't be disabled. Nevertheless, I suggest that you check if the extension is disabled by searching for "Tags" under "Extensions" -> "Manage".
My guess is that the folder administrator/components/com_tags folder is missing (or doesn't have the necessary read permissions) or you have some corruption in your assets table. Use the ACL Manager to fix the latter, and copy the com_tags folder from a fresh Joomla install (and fix the permissions) in the case of the former.
Related
After upgrading the joomla site iam getting the following error and administrator page is blank.
Fatal error: Can't use function return value in write context in /home/cll/public_html/libraries/regularlabs/src/File.php on line 283
Please help me to solve this issue.
It's clear that the problem comes from a regularlabs extension so you should disable it.
Since your admin page is blank, you can do this via the file system. Log in to your FTP account (or use the control panel's file manager) and access your root folder (/home/cll/public_html/). The extension you are looking for is probably a plugin so you'll find it in the plugins folder. I assume you'll find the extension in the /plugins/system/ folder (full path: /home/cll/public_html/plugins/system/).
When you'll find the extension's folder look for the plugin's PHP file and rename it.
For example, if the problem comes from "components anywhere" plugin (it's a regularlabs extension) search for componentsanywhere.php and rename it to something else (eg foobar.php).
If this doesn't help contact the developer to help you, he is a good guy.
I installed a new template for my joomla site but after that I have no access template manager. It only becomes a completely white page in Firefox and Opera says that "currently unable to handle the request." Is there any way to delete a template outside of the webadmin interface?
You can delete through your ftp client like filezilla. Open filezilla, login to your server and the delete the template. May be the template comes with some plugins or else how can just by installing it started showing error unless you use that template. Possibility is: i) You might have installed a template for older version. ii) You might have installed a plugin with the template that was autopublished. iii) You messed up some setting files.
I suggest you to open file manager, go to templates and then delete that particular template. Also when asking please ask providing all details like name of template, link of template etc.
I have a strange issue. When added a new domain to my site, "latest news enhaced" module started to appear truncated, it does not show the calendar and has a different style. For your reference : original installation http://myxolargos.gr/ilioupolis/
addon domain http://www.ilioupoli.gr/
I have tried to uninstall and install from new domain, but again it doesn't work properly in ilioupoli.gr It obviously has to do with a path somewhere?
Any ideas?
Thank you.
This has happened to me before. What fixed the problem for me was to turn "Search Engine Friendly URLs and Use URL Rewriting" off.
Navigate the site on the frontend, to the area affected.
Then turn "Search Engine Friendly URLs and Use URL Rewriting" on.
The issue is related to this stylesheets, one for each module:
/ilioupolis/modules/mod_latestnewsenhanced/stylemaster_238.css
/ilioupolis/modules/mod_latestnewsenhanced/stylemaster_239.css
/ilioupolis/modules/mod_latestnewsenhanced/stylemaster_240.css
Removing them from the original install removes the css rules that handle calendar date and position of the green text (like the new install). So check this files in the new install and you will find the problem.
I'm trying to edit the default core module named mod_weblinks to change how the list of weblinks within a category is shown.
The problem comes when I change the default.php file in modules/mod_weblinks/tmpl/ and I get no results when hit f5.
I also tried to copy and odify this file in template/my_template/html/mod_weblinks/ but same result.
I uninstalled and installed this module from joomla! control admin panel.
Any suggestion?
TIA
Ok, I found it, the problem is that I was modifying a module but using a component so I have change the code of the component (which is a bit more complex)
I've successfully installed Fishpig's Magento WordPress Integration extension. I followed the instructions where you install via Magento Connect and had no problems. This is by the way all on the development server which does not have Caching or Compiling enabled.
The Magento cart is installed in the webroot directory and WordPress is in subdirectory "wp" as stated in Fishpig's instructions. The Full Integration blog path is /blog.
PROBLEM:
When I visit the blog's page it is not using the Magento theme. I even set it to use the same layout (same as CMS's homepage) We have a custom Magento theme. Maybe there is something we are doing incorrectly Magento theme wise for Fishpig's extension not to work. Screenshots to come eventually but the host (DataGram) is down due to the flooding Downtown. Should be back hopefully today.
To clarify... WordPress is using its own database. In the Shop's admin panel->WordPress tab I setup Full Integration and set the path to "wp" and the blog path is blog.
So, now if I visit for example... example.com you are in the shop and if you visit example.com/blog you are in the fully integrated blog.
Bottom line is it seems to be configured fine in the admin panel. I am not requesting the blog page from the wp directory (I.E: example.com/wp) but from the fully integrated page (example.com/blog).
Our problem could be similar to what this person is experiencing:
Magento - FishPig Integration - Not getting correct template for /blog
Have a great weekend all!
Best Regards,
George
Huzzah looks like I got things working :-)
The culprit was that this file:
"app/design/frontend/default/eboost/layout/wordpress.xml"
^^ was pointing to the wrong template filename. Corrected and was good to go. Modified line was number 66.
Funny thing is that on the top of that XML file it states:
"
Option 1 - local.xml (recommended)
Create a file named local.xml in your custom theme's layout folder. You can then make changes to the layout there by
using the relevant layout handle. This allows you to leave this file intact and recieve new features
when upgrading the extension.
Option 2 - copy this file
Copy this file and it's contents to a new file in your custom theme's layout folder named wordpress.xml.
Each time you upgrade, you will need to check with your copy of the file and
the copy in app/design/frontend/base/default/layout/wordpress.xml for changes and merge any you find"
Now, as stated in my Original Posting I installed FishPig extension using their instructions: http://fishpig.co.uk/wordpress-integration/docs/installation-and-configuration.html
^^ Therefore I don't know why it is setup using Option 2. That wordpress.xml is in our theme's layout directory.
.
.
.
I feel I should also state the other changes I did even though it doesn't seem like it contributed to making it work. Just doing for completeness:
-- Renamed the subdirectory /wp to /wordpress and changed all references to dev.eboost.com/wp to dev.eboost.com/wordpress within the DataBase using http://interconnectit.com/124/search-and-replace-for-wordpress-databases/
-- Removed .htaccess from /wordpress folder
So bottom line is looks like it is working normally. We are now set for working on redesign for site.
--George
Have a look at this.
http://www.wellicious.com/gbren/wellblog
I also used Fishpig and it is working.
What do you mean by visiting the blog page? Do you request the blog page from the wordpress directory?
If so, it doesn't change its design.
You have to request the blog within your shop.