I've confirmed you at the user level but someone wit more access will need to approve your post.
indicates something is interferring with your paths
what is your default path?
a custom content type
a custom taxonomy
views to generate lists based on that taxonomy
themeing skills to theme your site to look similar.
likely need to plug in with the drupal commerce team https://drupalcommerce.org/
please edit your post and move it to the 'post installation' forum.
May also benefit to mention whether you are seeking to move content?, configuration? or both?
Please edit your post and move it to the 'post installation' forum.
It may also aid in mentioning what modules are in use to set up the store since D7 does not ship with any commerce as part of core.
check your post_max_size setting in php.ini, should always be higher than max_file_size
https://www.drupal.org/node/3348348 → may be helpful
test yoursite.com/?q=user/login - If that works your apache rewrite module is likely not enabled for clean urls to work.
you will need to inspect CSS of the element in question and adjust the CSS
create an event content type
use views to generate the list of events
release notes on the project page provide a list of changes.. example @ https://www.drupal.org/project/drupal/releases/11.0.3 →
why are you adding your name to the subject of every post?
https://www.drupal.org/project/issues/tara?categories=All → = where to report issues with the tara theme.
theme will also need to be Drupal 10. This you will need to update the existing theme if you intend to keep it.
mysite.com/admin/login is the correct login path
mysite.com/user/login is the correct login path
https://www.drupal.org/project/business → is what you're using?
sounds like the theme is disabling the default core tabs which would be odd for a theme here on drupal.org. I cannot find the catalog+ theme but did find a catalog lite theme. Can you provide a link to the theme in use?
use drupal's native installer rather than your hosts to eliminate this as a possible issue.
Sites that 'suddenly' stop working should be investigate more. Did you pull the site down into a local environment to test? Did it then work? if so, then what may have changed at the host over the horizon?
websites aren't set it and forget it. There is a great deal of software running underneath any one CMS that can have impact on the CMS.
For any part of core utilizing jquery, removal of that library will have an impact on those features at a minimum.
gallery - if you want a lightbox you will either have to use a module or write your own. There is not a 'lightbox style feature' in core.
or I just didn't feel you were deserving of my time.
you would add a link to your view pulling the data and then style it with CSS to look like a button.
okeedoke. best wishes.
https://www.drupal.org/docs/develop/theming-drupal/twig-in-drupal/workin... →
default drupal uses a view for the front page. you will need to create your own with a custom theme file if you don't want the default.
would help a great deal if you provided links. I have no idea what umami is.
adding blocks on a front page are done via the block administration ui.
blocks can only be set in 'regions' of a theme. Therefore if you wanted the blocks laid out differently from the default front page, you would add those regions to your theme and use a custom front page theme file
a button on an image? Do you mean make an image that is linked? If yes, linked to where?
I wouldn't blame the markdown module since its in use on many sites without issue. I just tested it without issue worked perfectly fine.
That said, every site is different and the more modules added the more complexity that must be expected by any one module developer.
A better path would be to do a deeper dive.
The link that Jaypan provided doesn't seem to work correctly
https://www.drupal.org/project/markdown → is the corrected link.
to hotlink images from Wiki Commons (or any site) into your Drupal node, you would need the whole path of the rendered images. Most sites don't like this tactic as you will use their resources to render the images. To avoid blacklisting you can download the images and upload them to your site and use your resources.
which project is installed? the one that is no longer maintained of the LTS version? If the former, remove it and install the LTS version.
https://www.drupal.org/project/ckeditor → is no longer maintained and based on the errors it doesn't run on PHP 8
https://www.drupal.org/project/ckeditor_lts → should be the ckeditor 4 in use
https://www.drupal.org/project/ckeditor → is no longer maintained and based on the errors it doesn't run on PHP 8
https://www.drupal.org/project/access_token_auth → is the only thing I can find but that seems to fall short of your use case. May have to write your own module.
a link to the theme in use would be helpful. A quick search turns up multiple themes that can be referred to as the 'mag theme'
you can use a content type for data gathering, storage and display
https://www.drupal.org/project/issues/external_entities?categories=All →
As the module in use is still in alpha and beta, I suggest filing an issue in the issue queue of the project in question
https://www.drupal.org/project/amplify →
The OpenAmplify service appears to have gone dark, please do not use this module or request support for it! Thanks for using it while it was active!
drupal contains its .htaccess files however drupal will not configur apache for you.
first thing to check is if mod_rewrite in apache is enabled. If not, it needs to be.
What documentation are you following?
Was the site initially installed with composer?
What about solving the SSL issues then performing the task in the recommended way?
summary is enabled by default when you create a content type with a summary field. none of my content types have summary fields, all use the default teaser configuration which does not include a summary field (different kind of content type).
It remains unclear to me if you are intentionally attempting to use summaries, or just want default teasers.
per https://sinet.ca/drupal10test/blog-manage-fields-edit.jpg
you are forcing an explicit summary. Thus, you won't get autogenerated teasers.
Summary text and teasers are often used interchangeably but aren't 'exactly' the same thing.
Need to know what fields are in use in the content type and how those fields are configured. Screenshots may help.
Good Day. It's been asked before @ https://www.drupal.org/forum/support/post-installation/2024-05-18/how-to... →
Why are you posting your name in the post titles and the post body? The question itself isn't directly related to Drupal. You failed to mention exactly what your challenges were. etc.
suggest your tmp folder be moved above the domain rather than in the domain. There is no reason the tmp folder needs to be publicly accessible.
no. a server environment on your laptop not on verizon.
https://www.drupal.org/docs/getting-started/installing-drupal →
yes. That said, it isn't just Drupal you will need. Drupal requires a server environment to run.
check index.php
if not there search all files for a single word in the
https://www.drupal.org/project/computed_field → may be a better option
you cannot upload images to forum posts on drupal.org. uploaded to a 3rd party photosharing site and share the link.
I suggest a review of the issue queue to see if others have similar experience. If none, create one. Please ensure you submit a screenshot of the visual problem.
https://www.drupal.org/project/issues/bootstrap_barrio?categories=All →
Can you please elaborate on the issue. As it stands now, there is not enough information here.
there are many things that can be causing an email issue. Is your MX record set up? is your website email getting caught in spam filters etc.
yes there are modules in contrib that can be used to aid in reducing spam submissions. Capctha, honeypot etc. Easily found with a search.
that makes me wonder if something 'odd' didn't occur during the last operation on that field that created the 'buggy state'. Weird in an interesting way.
and if you were to remove what was added, does it go back to the buggy state?
what was the site name that didn't work properly? curious if its special characters causing some issue that isn't widespread.
what was the site name that didn't work properly? curious if its special characters causing some issue that isn't widespread.
have you taken any time to research modules in contrib? You will not get any guarantees on a lifetime of any modules or themes or core.
https://drupal.stackexchange.com/questions/293288/can-views-output-raw-t... may aid? in that you can use a rewrite in the view using the raw token which should then send to the twig template raw?
I'd set up a test site with a core theme that only includes the module in question and its dependencies. if it works we can them determine why the theme in use isn't displaying the link. If it doesn't work on a core theme, then you should report the issue in the issue queue of the module in question @ https://www.drupal.org/project/issues/addtocal_augment?categories=All →
Rebuild in Drupal then migrate the users and content.
yes. As anything core or contrib would be worked through in issue queues rather than forums for alpha/beta builds.
I assume you are using https://www.drupal.org/project/bootstrap_layout_builder → ?
If yes, you must use a bootstrap theme. Olivero is not a bootstrap theme.
This question is best served in the 'general discussion' forum. Please edit your post and move it.
certainly odd but nothing drupal.org is doing. Suggest reaching out to developers of the audacious player to inquire.
suggest posting the rendered HTML for the entirety in a code block
support will need to come from zymphonies. Looks like a mismatch in the version of PHP in use version the version of PHP the 'package' was built on.
remove Drupal from the equation. Does the subdomain work correctly with a HELLO WORLD index.html file?
If the code is working without errors , it isn't 'wrong'. You mention litttle about how you implemented so no comment there.
If what you are doing is working for you that's great. I may have used something like https://www.drupal.org/project/floating_block → for the feature you implemeneted.
check all error logs (php, apache, drupal logs in database if necessary).
If on dev, roll your db back to before you enabled the module. Find the exact failure point and report the issue is its reproducable.
a custom block module to disable caching the block is possible.
in general yes, but again, it should be tested on a test upgrade before production as noone here can know of any custom code, or module impact.
From UPDATE.txt included in Drupal 7
INTRODUCTION
------------
This document describes how to:* Update your Drupal site from one minor 7.x version to another minor 7.x
version; for example, from 7.8 to 7.9, or from 7.6 to 7.10.* Upgrade your Drupal site's major version from 6.x to 7.x.
First steps and definitions:
* If you are upgrading to Drupal version x.y, then x is known as the major
version number, and y is known as the minor version number. The download
file will be named drupal-x.y.tar.gz (or drupal-x.y.zip).* All directories mentioned in this document are relative to the directory of
your Drupal installation.* Make a full backup of all files, directories, and your database(s) before
starting, and save it outside your Drupal installation directory.
Instructions may be found at http://drupal.org/upgrade/backing-up-the-db* It is wise to try an update or upgrade on a test copy of your site before
applying it to your live site. Even minor updates can cause your site's
behavior to change.* Each new release of Drupal has release notes, which explain the changes made
since the previous version and any special instructions needed to update or
upgrade to the new version. You can find a link to the release notes for the
version you are upgrading or updating to on the Drupal project page
(http://drupal.org/project/drupal).UPGRADE PROBLEMS
----------------
If you encounter errors during this process,* Note any error messages you see.
* Restore your site to its previous state, using the file and database backups
you created before you started the upgrade process. Do not attempt to do
further upgrades on a site that had update problems.* Consult one of the support options listed on http://drupal.org/support
More in-depth information on upgrading can be found at http://drupal.org/upgrade
MINOR VERSION UPDATES
---------------------
To update from one minor 7.x version of Drupal to any later 7.x version, after
following the instructions in the INTRODUCTION section at the top of this file:1. Log in as a user with the permission "Administer software updates".
2. Go to Administration > Configuration > Development > Maintenance mode.
Enable the "Put site into maintenance mode" checkbox and save the
configuration.3. Remove all old core files and directories, except for the 'sites' directory
and any custom files you added elsewhere.If you made modifications to files like .htaccess or robots.txt, you will
need to re-apply them from your backup, after the new files are in place.Sometimes an update includes changes to default.settings.php (this will be
noted in the release notes). If that's the case, follow these steps:- Locate your settings.php file in the /sites/* directory. (Typically
sites/default.)- Make a backup copy of your settings.php file, with a different file name.
- Make a copy of the new default.settings.php file, and name the copy
settings.php (overwriting your previous settings.php file).- Copy the custom and site-specific entries from the backup you made into the
new settings.php file. You will definitely need the lines giving the
database information, and you will also want to copy in any other
customizations you have added.You can find the release notes for your version at
https://www.drupal.org/project/drupal → . At bottom of the project page under
"Downloads" use the link for your version of Drupal to view the release
notes. If your version is not listed, use the 'View all releases' link. From
this page you can scroll down or use the filter to find your version and its
release notes.4. Download the latest Drupal 7.x release from http://drupal.org to a
directory outside of your web root. Extract the archive and copy the files
into your Drupal directory.On a typical Unix/Linux command line, use the following commands to download
and extract:wget http://drupal.org/files/projects/drupal-x.y.tar.gz
tar -zxvf drupal-x.y.tar.gzThis creates a new directory drupal-x.y/ containing all Drupal files and
directories. Copy the files into your Drupal installation directory:cp -R drupal-x.y/* drupal-x.y/.htaccess /path/to/your/installation
If you do not have command line access to your server, download the archive
from http://drupal.org using your web browser, extract it, and then use an
FTP client to upload the files to your web root.5. Re-apply any modifications to files such as .htaccess or robots.txt.
6. Run update.php by visiting http://www.example.com/update.php (replace
www.example.com with your domain name). This will update the core database
tables.If you are unable to access update.php do the following:
- Open settings.php with a text editor.
- Find the line that says:
$update_free_access = FALSE;- Change it into:
$update_free_access = TRUE;- Once the upgrade is done, $update_free_access must be reverted to FALSE.
7. Go to Administration > Reports > Status report. Verify that everything is
working as expected.8. Ensure that $update_free_access is FALSE in settings.php.
9. Go to Administration > Configuration > Development > Maintenance mode.
Disable the "Put site into maintenance mode" checkbox and save the
configuration.MAJOR VERSION UPGRADE
---------------------
To upgrade from a previous major version of Drupal to Drupal 7.x, after
following the instructions in the INTRODUCTION section at the top of this file:1. Check on the Drupal 7 status of your contributed and custom modules and
themes. See http://drupal.org/node/948216 for information on upgrading
contributed modules and themes. See http://drupal.org/node/895314 for a list
of modules that have been moved into core for Drupal 7, and instructions on
how to update them. See http://drupal.org/update/modules for information on
how to update your custom modules, and http://drupal.org/update/theme for
custom themes.You may decide at this point that you cannot upgrade your site, because
needed modules or themes are not ready for Drupal 7.2. Update to the latest available version of Drupal 6.x (if your current version
is Drupal 5.x, you have to upgrade to 6.x first). If you need to update,
download Drupal 6.x and follow the instructions in its UPGRADE.txt. This
document only applies for upgrades from 6.x to 7.x.3. In addition to updating to the latest available version of Drupal 6.x core,
you must also upgrade all of your contributed modules for Drupal to their
latest Drupal 6.x versions.4. Log in as user ID 1 (the site maintenance user).
5. Go to Administer > Site configuration > Site maintenance. Select
"Off-line" and save the configuration.6. Go to Administer > Site building > Themes. Enable "Garland" and select it as
the default theme.7. Go to Administer > Site building > Modules. Disable all modules that are not
listed under "Core - required" or "Core - optional". It is possible that some
modules cannot be disabled, because others depend on them. Repeat this step
until all non-core modules are disabled.If you know that you will not re-enable some modules for Drupal 7.x and you
no longer need their data, then you can uninstall them under the Uninstall
tab after disabling them.8. On the command line or in your FTP client, remove the file
sites/default/default.settings.php
9. Remove all old core files and directories, except for the 'sites' directory
and any custom files you added elsewhere.If you made modifications to files like .htaccess or robots.txt, you will
need to re-apply them from your backup, after the new files are in place.10. If you uninstalled any modules, remove them from the sites/all/modules and
other sites/*/modules directories. Leave other modules in place, even though
they are incompatible with Drupal 7.x.11. Download the latest Drupal 7.x release from http://drupal.org to a
directory outside of your web root. Extract the archive and copy the files
into your Drupal directory.On a typical Unix/Linux command line, use the following commands to download
and extract:wget http://drupal.org/files/projects/drupal-x.y.tar.gz
tar -zxvf drupal-x.y.tar.gzThis creates a new directory drupal-x.y/ containing all Drupal files and
directories. Copy the files into your Drupal installation directory:cp -R drupal-x.y/* drupal-x.y/.htaccess /path/to/your/installation
If you do not have command line access to your server, download the archive
from http://drupal.org using your web browser, extract it, and then use an
FTP client to upload the files to your web root.12. Re-apply any modifications to files such as .htaccess or robots.txt.
13. Make your settings.php file writeable, so that the update process can
convert it to the format of Drupal 7.x. settings.php is usually located insites/default/settings.php
14. Run update.php by visiting http://www.example.com/update.php (replace
www.example.com with your domain name). This will update the core database
tables.If you are unable to access update.php do the following:
- Open settings.php with a text editor.
- Find the line that says:
$update_free_access = FALSE;- Change it into:
$update_free_access = TRUE;- Once the upgrade is done, $update_free_access must be reverted to FALSE.
15. Backup your database after the core upgrade has run.
16. Replace and update your non-core modules and themes, following the
procedures at http://drupal.org/node/94821617. Go to Administration > Reports > Status report. Verify that everything is
working as expected.18. Ensure that $update_free_access is FALSE in settings.php.
19. Go to Administration > Configuration > Development > Maintenance mode.
Disable the "Put site into maintenance mode" checkbox and save the
configuration.To get started with Drupal 7 administration, visit
http://drupal.org/getting-started/7/admin
This would likely need to be started in contrib before it would be available to core. I did a quick search and don't see any specific core initiatives for this. Perhaps discussing in the issue queue of the 2FA modules to learn if any of those are working toward providing MFA.
similar issues found with solutions to attempt:
https://www.drupal.org/project/mysql56/issues/3316955 📌 documentation - error message Active
https://www.drupal.org/forum/support/post-installation/2022-11-24/just-c... →
https://drupal.stackexchange.com/questions/316487/is-the-libmysqlclient-...
strip out the CSS manually. There is nothing in core of contrib that will strip existing CSS from stylesheets.
I'm not sure what initial means in the context of use above. Perhaps, a screenshot linked to your post of what you are seeing, and a mockup of what you want to see if best?
I'd consider a relative URL
I'd visit the default url in your menus to determine the correct path
in ckeditor you can use - https://www.drupal.org/project/editor_advanced_link → or https://www.drupal.org/project/linkit →
in your menus you can add a a target="blank" to the URL of the menu link.