drgene113

Hee is a response I received from the theme developer:

We analyzed the issue and found out that we cannot (even with tweaks) make the component coming from ‘Forminator’ on the survey (mentioned by you), clickable (when we remove the eLumine styling).
The changes in the code need to be made to the plugin to handle this issue.

Did the ‘Forminator’ Support team face this same issue? I kindly request you to address this issue to them (about the ‘Forminator’ component not being clickable once the CSS is added) and ask them to resolve it. In case, they require any changes from our side, we will definitely take care of that.

To give you better insight, let me explain this in more detail:
When we removed the Forminator Styling, the same issue was faced by us (the ‘eLumine’ component not being clickable once the CSS is added), but we made changes to the theme accordingly and the issue was resolved.
On the other way around, vice versa happens when we make the changes to the plugin. This needs to be handled by them.

I was told that thus feature will be included in a future update. They can also code it with the “Do it for me” Plan

Gene

Thanks again for all your help!

thanks

I did this and it seemed to work:
I created class files in the wp-content/uploads directory

Then renamed the links from /classes/subject1
to /wp-content/uploads/subject1/name-of-file

Sounds good.
When I copy this text to the wordpress page in html format, will it work (maintain the correct links)?

Yes, it needs to be on a page.

I have a set of classes that I teach and want my students to be able
to go to a “class” page and see downloadable files laid out week by
week.

If you don’t mind, I have two more questions:

1. I am redireccting 6 subdirectories from one domain to 6 on a different domain. Could I just enter and edit the appropriate code 6 times?

2. Where in the .htaccess fle does the code go?

I already see this code in the file:

#— DH-PHP handlers —
AddHandler fastcgi-script fcg fcgi fpl
AddHandler php-fastcgi .php
Action php-fastcgi /cgi-bin/dispatch.fcgi

##
# @version $Id: htaccess.txt 14401 2010-01-26 14:10:00Z louis $
# @package Joomla
# @copyright Copyright (C) 2005 – 2010 Open Source Matters. All rights reserved.
# @license https://www.gnu.org/copyleft/gpl.html GNU/GPL
# Joomla! is Free Software
##
#####################################################
# READ THIS COMPLETELY IF YOU CHOOSE TO USE THIS FILE
#
# The line just below this section: ‘Options +FollowSymLinks’ may cause problems
# with some server configurations. It is required for use of mod_rewrite, but may already
# be set by your server administrator in a way that dissallows changing it in
# your .htaccess file. If using it causes your server to error out, comment it out (add # to
# beginning of line), reload your site in your browser and test your sef url’s. If they work,
# it has been set by your server administrator and you do not need it set here.
#
#####################################################
## Can be commented out if causes errors, see notes above.
## Options +FollowSymLinks
#
# mod_rewrite in use
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteCond %{HTTP_HOST} !^www\..*
RewriteCond %{HTTP_HOST} !^$
RewriteCond %{HTTP_HOST} ^([^.]*)\.(org|com)
RewriteRule ^.*$ https://www.%1.%2%{REQUEST_URI} [R=permanent,L]
RewriteCond %{SERVER_PORT} 443
RewriteCond %{HTTP_HOST} !^www\..*
RewriteCond %{HTTP_HOST} !^$
RewriteCond %{HTTP_HOST} ^([^.]*)\.(org|com)
RewriteRule ^.*$ https://www.%1.%2%{REQUEST_URI} [R=permanent,L]
########## Begin – Rewrite rules to block out some common exploits
## If you experience problems on your site block out the operations listed below
## This attempts to block the most common type of exploit attempts to Joomla!
#
## Deny access to extension xml files (uncomment out to activate)
#<Files ~ “\.xml$”>
#Order allow,deny
#Deny from all
#Satisfy all
#</Files>
## End of deny access to extension xml files
RewriteCond %{QUERY_STRING} mosConfig_[a-zA-Z_]{1,21}(=|\%3D) [OR]
# Block out any script trying to base64_encode crap to send via URL
RewriteCond %{QUERY_STRING} base64_encode.*\(.*\) [OR]
# Block out any script that includes a <script> tag in URL
RewriteCond %{QUERY_STRING} (\<|%3C).*script.*(\>|%3E) [NC,OR]
# Block out any script trying to set a PHP GLOBALS variable via URL
RewriteCond %{QUERY_STRING} GLOBALS(=|\[|\%[0-9A-Z]{0,2}) [OR]
# Block out any script trying to modify a _REQUEST variable via URL
RewriteCond %{QUERY_STRING} _REQUEST(=|\[|\%[0-9A-Z]{0,2})
# Send all blocked request to homepage with 403 Forbidden error!
RewriteRule ^(.*)$ index.php [F,L]
#
########## End – Rewrite rules to block out some common exploits
# Uncomment following line if your webserver’s URL
# is not directly related to physical file paths.
# Update Your Joomla! Directory (just / for root)
# RewriteBase /
########## Begin – Joomla! core SEF Section
#
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !^/index.php
RewriteCond %{REQUEST_URI} (/|\.php|\.html|\.htm|\.feed|\.pdf|\.raw|/[^.]*)$ [NC]
RewriteRule (.*) index.php
RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]
#
########## End – Joomla! core SEF Section

Thanks so much I will try it.

So I would edit the .htaccess file found under the https://www.mmti.org main directory?

Would this work if I enter teh appropriate website addresses?

Redirect to www (htaccess redirect)

Create a .htaccess file with the below code, it will ensure that all requests coming in to domain.com will get redirected to https://www.domain.com
The .htaccess file needs to be placed in the root directory of your old website (i.e the same directory where your index file is placed)

Options +FollowSymlinks
RewriteEngine on
rewritecond %{http_host} ^domain.com [nc]
rewriterule ^(.*)$ https://www.domain.com/$1 [r=301,nc]

Hi,
I actually found that site but still am confused.

Thanks so much; that did the trick.

Much appreciated.
Gene

Ok thats done.
Then I copied and pasted the code generated thatnisntombe entered into and htaccess file.

I created a file called htaccess.rtf with the code inside it.
I uploaded it to the root directory and then renamed it to .htaccess

when I do that my site crashes and give an internal service error

Gene

Thanks.
Doess the code define(‘WP_ALLOW_MULTISITE’, true); need to be included in the wp-config.php file? Or was it ok to delete it before I added the new 20 lines of code as instructed in the. Tools–>network setup

I am geting the same result.
My meta code is:

<meta name=”verify-v1″ content=”vrbGuqr0VAFkFsiDcVfuU+xi33byWmrXb/Trn7vqq9o=” >

Do I insert the exact string into the meta robots plugin section for google webmaster tools or the part between the quotes?

No matter what I enter, after saving, I get the following code in the box:

<meta name=\ />

Thanks for the info. I also received some advice about restricting pages based on categories using one wordpress intalaation.
what would be an advantage of using WordPress MU if I will be the only person adding content.
Thanks
gene